You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
since I'm also facing this issue constantly (also with ' char) I've checked the linked repository and it seems that is completely abandoned - the last commit is from 9 years ago and none of the submitted PR's was merged. This indicates that the problem/bug might persist forever.
If the ini syntax highlighting grammar was taken from this repo a long time ago then why it can't be fixed/updated by VSCode team? Can you re-open this issue and suggest a new approach how to fix it?
@ALIENQuake it's hard for a smallish team like the VS Code team to be experts in every language we want to provide syntax highlighting for, so we won't be updating the grammar ourselves. However, we've had several abandoned grammar repos in recent years that members of the community have offered well maintained alternatives for (a1481e3, #115480, and #140489). If the owner of a well maintained ini textmate grammar asks that we try using their grammar instead then I'd be happy to consider adopting it!
In the mean time maybe there is an extension you can install that will provide better syntax highlighting for your ini files. As a last resort, you can disable the built in ini extension too.
@ALIENQuake a separate repository is required. Some evidence that the new grammar will continue to be maintained is also very helpful (for example, a history of maintaining the grammar as part of an extension).
@alexr00
Hello,
since I'm also facing this issue constantly (also with
'
char) I've checked the linked repository and it seems that is completely abandoned - the last commit is from 9 years ago and none of the submitted PR's was merged. This indicates that the problem/bug might persist forever.If the ini syntax highlighting grammar was taken from this repo a long time ago then why it can't be fixed/updated by VSCode team? Can you re-open this issue and suggest a new approach how to fix it?
Originally posted by @ALIENQuake in #139531 (comment)
The text was updated successfully, but these errors were encountered: