-
Notifications
You must be signed in to change notification settings - Fork 5
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
issue with quoted comment marker #14
Comments
Just wanted to note that this is still bugging me, I've tried to have a "more or less quick" look at the definition but neither "comment" nor "#" are good search criterias in the tmLanguage definition for autoconf. Any hint where to look at? |
So sorry I didn't get to come back to you before :( Could you try to open a PR with the change? I would greatly appreciate it! |
I'd love to pull anything but I have no clue where to do the change. Help/hints wanted... (I could then investigate and test and PR)
|
No problem! I added a bit of help in the readme if you want to check it out 😀 |
Hmmm I think I know where the bug comes from... it does not seem to be due to the grammar itself (Autoconf.YAML-tmLanguage). I would guess it comes from how VSCode parses comments: vscode_autotools/language-configuration.json Lines 2 to 5 in dc6849f
|
Nope, doesn't look like an issue with Works: PKG_CHECK_MODULES([CJSON], [#]) Breaks: PKG_CHECK_MODULES([CJSON], [], [#]) I'm clueless 🙁 |
Is this an upstream issue? |
Some entries actual need an empty "on error do nothing" to override the default behavior (likely of stopping with an error).
A good sample is likely:
this extension does not stop the inline comment and therefore assumes the macro parameters are not correctly closed, which makes editing all following lines bad (full of red errors and no option to match brackets correct)
The text was updated successfully, but these errors were encountered: