-
Notifications
You must be signed in to change notification settings - Fork 19
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
Less aggressive comment highlighting #19
Comments
Hey - I'll try and take a look at this over the next week or so. I'll need to work out how to do it, but I'll try to figure it out 🙂 |
Sorry for the delay in coming back on this, unfortunately there appears to be no simple way of adding this as a configuration option currently. Comments and syntax fall under declarative language features rather than programmatic. So VSCode doesn't provide an option, as of yet, to easily modify them on the fly. I'll leave this issue open though, and will add this feature if VSCode provides a hook that can be easily used in the future. |
Encountering the same issue, GAS uses ; the same as C, as a linebreak, so you can have multiple statements on a single line, which here is marks the entire line as a comment. Edit: Is there any relevant issues open on VSCode you're aware of talking about this limitation? |
Nope - but I've just opened one and referenced this issue 🙂 |
Currently, the extension marks
@
or;
to end of line as a comment, which can be problematic when an assembler only uses one for comments and uses the other as part of labels. Adding a workspace-level configuration option to change comment character(s) for highlighting would resolve this.The text was updated successfully, but these errors were encountered: