EditorSyntax
code-settings-sync
EditorSyntax | code-settings-sync | |
---|---|---|
5 | 6 | |
123 | 4,001 | |
2.4% | - | |
0.0 | 0.0 | |
over 2 years ago | about 2 months ago | |
PowerShell | TypeScript | |
MIT License | MIT License |
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
-
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.
code-settings-sync
-
How and Why I Stopped Buying New Laptops
https://github.com/shanalikhan/code-settings-sync/issues/136...
-
How long has Settings Sync been deprecated ? Can't find anything online
The last commit on the Settings Sync repo was late 2019, so it was probably deprecated around that time.
-
I'm a long time Vim user, and I want to move to VS Code for a while. I like to script my editor a lot (PDE-style). How should I approach this?
Note: If you do, be aware of this bug and workaround.
- Settings not syncing into VS code
-
Is Settings sync extension dead?
settings sync: https://github.com/shanalikhan/code-settings-sync
-
What do you guys do to setup Visual Studio Code for PowerShell?
I don't use the built-in one, I use an extension called Settings Sync.
What are some alternatives?
dbatools - 🚀 SQL Server automation and instance migrations have never been safer, faster or freer
vscode-wakatime - Visual Studio Code plugin for automatic time tracking and metrics generated from your programming activity.
PSScriptAnalyzer - Download ScriptAnalyzer from PowerShellGallery
vscode-git-graph - View a Git Graph of your repository in Visual Studio Code, and easily perform Git actions from the graph.
vscode-powershell - Provides PowerShell language and debugging support for Visual Studio Code
vscode-zig - Zig language support for VSCode
PSResourceGet - PSResourceGet is the package manager for PowerShell
ethereum-code-viewer - View source of deployed Ethereum contracts in VSCode [Moved to: https://github.com/dethcrypto/dethcode]
dethcode - View source of deployed Ethereum contracts in VSCode
vscode-crystal-lang - Yet another VSCode extension for Crystal Programming Language
vscode-restclient - REST Client Extension for Visual Studio Code
vscode-intelephense - PHP intellisense for Visual Studio Code