We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I am using skylighting 0.12.3.1.
I have the following example file:
(define-syntax grammar (syntax-rules (→) ((_ (left1 → right11 right12 ...) (left2 → right21 right22 ...) ...) (vector (production left1 → right11 right12 ...) (production left2 → right21 right22 ...) ...)))) (define grammar-production vector-ref) (define (grammar-production-number g p) (let ((l (vector-length g))) (let loop ((i 0)) (if (>= i l) #f (if (equal? (grammar-production g i) p) i (loop (+ i 1)))))))
I run the following command:
skylighting -f native -s scheme test.scm
The first define works fine although I do not understand, why the white-space is part of FunctionTok:
FunctionTok
, [ ( NormalTok , "(" ) , ( ExtensionTok , "define" ) , ( FunctionTok , " grammar-production " ) , ( KeywordTok , "vector-ref" ) , ( NormalTok , ")" ) ]
But the second definition does not work:
, [ ( NormalTok , "(" ) , ( ExtensionTok , "define" ) , ( FunctionTok , " " ) , ( NormalTok , "(grammar-production-number g p)" ) ]
The FunktionTok contains just the white-space.
FunktionTok
The text was updated successfully, but these errors were encountered:
Seems to be an upstream bug: https://bugs.kde.org/show_bug.cgi?id=476879
Sorry, something went wrong.
Let us know when it's fixed upstream.
No branches or pull requests
I am using skylighting 0.12.3.1.
I have the following example file:
I run the following command:
The first define works fine although I do not understand, why the white-space is part of
FunctionTok
:But the second definition does not work:
The
FunktionTok
contains just the white-space.The text was updated successfully, but these errors were encountered: