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
I was recently following up an issue on a bug for an HTML syntax highlighting issue, and found out it was closed as waiting for upstream (TextMate bundle) to fix the issue.
There is this information for contributors above some language grammars that depend on TextMate bundles:
I wanted to inform that TextMate (and all of its grammar bundles are not being maintained anymore.
In October 2021, the latest/last commit was made to GitHub, though no announcement has been made to the effect that the project has been officially abandoned and its source code is still publicly available.
Here is a list of TextMate bundles Visual Studio Code depends upon and their latest update:
I don't necessarily mean they need active maintaining, but Visual Studio Code will miss language improvements and required bug fixes, and there will be lots of unnecessary housekeeping work required to clean up issues and PRs for those.
So with all that given, I believe it could be beneficial to developers using Visual Studio Code if we had an actively maintained language grammar.
I looked up to see if the same discussion is already open somewhere, but did not find any public discussion. The most similar, but still unrelated discussion was this:
All these issues/PRs all refer to the same bug and I used this bug only as an example. There are probably other issues with other grammar bugs here and there, which are probably open/closed without resolution because of the same reason.
The text was updated successfully, but these errors were encountered:
For many of these we are trying to find a new grammar. Others, we don't actually depend on:
YAML: Trying to find a new grammar.
XML: Trying to find a new grammar.
ASP.VB: We're not trying to find a new grammar here, but there aren't many complaints about it.
Ruby: We're not trying to find a new grammar here, but there aren't many complaints about it.
Perl: We're not trying to find a new grammar here, but there aren't many complaints about it.
ini: Trying to find a new grammar.
Groovy: Trying to find a new grammar.
Git: We have moved to a new grammar 1 year ago. The textmate repo grammar is only used for rebase now.
Diff: We're not trying to find a new grammar here, but there aren't many complaints about it.
c/cpp: We moved to new C and C++ grammars years ago. The textmate repo grammar is only included for source.c.platform, which is included by other languages.
Hi 👋
I was recently following up an issue on a bug for an HTML syntax highlighting issue, and found out it was closed as waiting for upstream (TextMate bundle) to fix the issue.
There is this information for contributors above some language grammars that depend on TextMate bundles:
I wanted to inform that TextMate (and all of its grammar bundles are not being maintained anymore.
This is also copied from the WikiPedia of TextMate:
Here is a list of TextMate bundles Visual Studio Code depends upon and their latest update:
I don't necessarily mean they need active maintaining, but Visual Studio Code will miss language improvements and required bug fixes, and there will be lots of unnecessary housekeeping work required to clean up issues and PRs for those.
So with all that given, I believe it could be beneficial to developers using Visual Studio Code if we had an actively maintained language grammar.
I looked up to see if the same discussion is already open somewhere, but did not find any public discussion. The most similar, but still unrelated discussion was this:
which is looking for alternatives to TextMate; but for reasons other than the fact that TextMate is dead. (?)
Example Case
I was following up on this issue recently:
which later was closed as a duplicate of this issue in the upstream TextMate language grammar for HTML:
//
have unexpected behavrio textmate/html.tmbundle#113Which later I followed on more issues being closed as duplicate of the same issue:
The issue is simply about a bug in HTML language grammar for event handler attributes. (which is not the topic here)
And there is a fix PR for it in the upstream repo:
and a closed PR (the same PR) in vscode repo:
All these issues/PRs all refer to the same bug and I used this bug only as an example. There are probably other issues with other grammar bugs here and there, which are probably open/closed without resolution because of the same reason.
The text was updated successfully, but these errors were encountered: