EditorSyntax
Syntax highlighting files for editors (VSCode, Atom, SublimeText, TextMate, etc) and GitHub! (by PowerShell)
vscode-powershell
Provides PowerShell language and debugging support for Visual Studio Code (by PowerShell)
| EditorSyntax | vscode-powershell | |
|---|---|---|
| 5 | 29 | |
| 123 | 1,653 | |
| 2.4% | 0.4% | |
| 0.0 | 9.4 | |
| over 2 years ago | 5 days ago | |
| PowerShell | TypeScript | |
| MIT License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
EditorSyntax
Posts with mentions or reviews of EditorSyntax.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-10-31.
-
How to change VSCode command color for aliases?
Serious answer: It depends on how much you care about it. At one point I used this WIP rewrite of the grammar: https://github.com/PowerShell/EditorSyntax/pull/156 + a custom theme to get it exactly how I want it but it was a bit of a pain to maintain across updates, new computers, etc. These days I just do most of my editing in ISE and only use VS code for minor tweaks.
-
Who uses Visual Studio Code for PowerShell Scripting?
There is a PR that mostly solves the inaccuracies here: https://github.com/PowerShell/EditorSyntax/pull/156 but it has been WIP since 2019 with no sign of him finishing it in the near future. I don't blame him because it's a ton of work and semantic highlighting sort of made it irrelevant but it does leave us without an official editor that can handle the PS6+ syntax.
-
What do you guys do to setup Visual Studio Code for PowerShell?
This is the grammar I'm using: https://github.com/PowerShell/EditorSyntax/pull/156 except I'm using the slightly modified version that is mentioned in the comments to properly highlight commands without the approved verb-noun syntax.
-
VS Code Syntax Highlighting
The beginning of the chaos was this commit https://github.com/PowerShell/EditorSyntax/commit/0cf060e9e0095e8e2565a3496d3909067b49fd90 which you'll notice contains no regex changes. It was things like changing the scope of $ from keyword.other.variable.definition.powershell to punctuation.definition.variable.powershell.
vscode-powershell
Posts with mentions or reviews of vscode-powershell.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-12-20.
-
Weird scriptlisting.ps1 tab appears
This file seems to be specific to the ps debugger apparatus ... https://github.com/PowerShell/vscode-powershell/issues/555
-
custom - powershell snippets using luasnip not working
downloaded and place a json file under /snippets/powershell from https://github.com/PowerShell/vscode-powershell/blob/main/snippets/PowerShell.json
- VS-Code Temporary Integrated Console not using any profile.ps1
- Weird issues with VS Code
-
Finally custom classes are somewhat usable with VSCode Powershell Preview Extension
v2023.2.0-preview
-
How do I get the Windows command line and Powershell to remember my last 100 commands?
The PowerShell extension for Visual Studio Code stores the history in the below location:
- VS Code Debugging: Returns Error Not In Script
-
Help with VS Code
Yeah, I had an issue like that, and it was because the extension didn't fully activate. Check out this issue on GitHub, it was about the same I was getting.
-
VSCode - PowerShell Extension: if running scripts changes your working directory and breaks dot sourcing, install the v2022.9.0 preview release
I had to do some digging, and found that the issue for this was resolved in the v2022.9.0 preview release.
-
VSCode re-writes my F8 command into the terminal prompt on it's own?
Today's release fixes this issue. https://github.com/PowerShell/vscode-powershell/issues/4041
What are some alternatives?
When comparing EditorSyntax and vscode-powershell you can also consider the following projects:
code-settings-sync - 🌴💪 Synchronize your Visual Studio Code Settings Across Multiple Machines using GitHub GIST 💪🌴
nvim-lsp-installer - Further development has moved to https://github.com/williamboman/mason.nvim!
dbatools - 🚀 SQL Server automation and instance migrations have never been safer, faster or freer
PSScriptAnalyzer - Download ScriptAnalyzer from PowerShellGallery
vetur - Vue tooling for VS Code.
PSResourceGet - PSResourceGet is the package manager for PowerShell
Open-Shell-Menu - Classic Shell Reborn.
PersistentWindows - fork of http://www.ninjacrab.com/persistent-windows/ with windows 10 update
notepad-plus-plus - Notepad++ official repository
Bitwarden - The core infrastructure backend (API, database, Docker, etc).
EditorSyntax vs code-settings-sync
vscode-powershell vs nvim-lsp-installer
EditorSyntax vs dbatools
vscode-powershell vs PSScriptAnalyzer
EditorSyntax vs PSScriptAnalyzer
vscode-powershell vs vetur
EditorSyntax vs PSResourceGet
vscode-powershell vs dbatools
vscode-powershell vs Open-Shell-Menu
vscode-powershell vs PersistentWindows
vscode-powershell vs notepad-plus-plus
vscode-powershell vs Bitwarden