Replace PowerShell grammar by a better one #4143
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Replace PowerShell grammar from using https://github.com/sublimetext/powershell to using https://github.com/PowerShell/EditorSyntax .
Description
In #2047 we switched to using https://github.com/sublimetext/powershell for the grammar.
Since then a new project got created: 1 project to rule all the powershell tmLanguage grammars.
https://github.com/PowerShell/EditorSyntax
Today ST switched to using EditorSyntax, and it doesn't make sense anymore to use ST grammar in linguist: it should go directly to EditorSyntax.
cc @omniomi @tylerl0706
Checklist:
I am associating a language with a new file extension.
I am adding a new language.
I am fixing a misclassified language
I am changing the source of a syntax highlighting grammar
I am adding new or changing current functionality