-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
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
Lexer options don't get passed to lexer #72
Comments
Hey @alexanderweiss 👋🏼 Would you like to send a patch? Better late than never 💪🏼. I think it makes sense what you mentioned in the comment above ☝🏼. |
Hello @alexanderweiss 👋🏼 Sorry for the ping! Just wanted to ask if you can help us to fix this one 🙏🏼 If you can send a patch, that would be amazing, otherwise if you can point me to the right docs I'll try to submit a patch (and a test) by myself. Would like to better understand what this ℹ️ I started some months ago to collaborate in the Middleman ecosystem, so I'm trying to catch up with old issues/PRs. |
Hey! Sorry for the delay. Haven't been using middleman in a while. But rouge's lexers are basically the language parsers that turn some input into a common format. Each individual lexer/parser accepts language-specific options. See e.g. the console lexer. These are passed to the lex function |
Lexer options, defined in config.rb don't seem to get passed to passed to the lexer:
The above doesn't actually override the default settings of the console lexer.
I've been trying to figure out what was going on and it seems like the lexer_options need to be passed as the third argument to find_fancy, rather than to lexer.lex (in https://github.com/middleman/middleman-syntax/blob/master/lib/middleman-syntax/highlighter.rb):
The text was updated successfully, but these errors were encountered: