-
Notifications
You must be signed in to change notification settings - Fork 453
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
Use scope instead of grammar name #764
Comments
This is a very interesting idea. Applicable code sections for someone who may want to try implementing this: |
Thanks! |
It seems that perhaps |
I'd love to see a Pull Request implementing something in this direction! Major changes are happening for #1174 and if this is the right direction then I would want this improvement to be in the next major release! Thanks in advance. |
This issue has been automatically marked as stale because it has not had recent activity. If this is still an issue, please add a comment. It will be closed if no further activity occurs. Thank you for your contributions. |
Using
editor.getGrammar().name
requires there to be a specific beautifier for the current grammar. This is unfortunate because of how scope extension and nesting works.Consider a templating language, e.g. "Smarty". Ideally I should be able to beautify as HTML in this grammar, as the
scopeName
istext.html.smarty
. However, since you're only using the grammar name, I have to switch grammars to be able to beautify.Related/Similar issue: emmetio/emmet-atom#376
The text was updated successfully, but these errors were encountered: