EditorSyntax
nvim-lsp-installer
EditorSyntax | nvim-lsp-installer | |
---|---|---|
5 | 82 | |
123 | 2,022 | |
2.4% | - | |
0.0 | 9.7 | |
over 2 years ago | over 1 year ago | |
PowerShell | Lua | |
MIT License | Apache License 2.0 |
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.
nvim-lsp-installer
- [Neovim] Présentation de mason.nvim
-
Unable to get a working setup for lsp
I had previous gotten a working setup with https://github.com/williamboman/nvim-lsp-installer however, I have been unable to get it working ever since.
-
How do you stay up-to-date on the plugins you use?
The only way to stay up to date, is when you read the commits if you update the plugins. In this case for the lsp-installer in the commit bfa74f4 was mentioned that the plugin will no longer maintained
-
LSP question: manage an already installed server (instead of using lspinstall)
A word of caution, I believe lspinstall has been deprecated in favor of nvim-lspinstall which itself has also been deprecated in favor of mason-lspconfig
-
AstroNvim 2.4
We have now migrated from nvim-lsp-instasller to mason which provides automatic LSP and null-ls configuration after installation
-
Best way to go about installing LSP today?
nvim-lsp-installer or mason.nvim. FYI lsp-zero also uses mason.nvim for managing installation.
-
Vue + Volar = Error Request initialize failed
I'm using nvim-lsp-installer it installs typescript when installing volar. So I had given it that path. Plus I had typescript locally installing since I'm using vue3+ts(vite) template
-
rust-analyzer changelog #146
Though mason only recently replaced nvim-lsp-installer. Same author but they decided to make a complete rewrite given the broader scope beyond only providing language servers. And nvim-dap had it's initial release in late July. The actual dap servers are all kind of mature since they've been running on vscode for a couple of years or more now - and the protocol is apparently almost as old as lsp. So when I call them beta, it's more a commentary on the state of the neovim side of the ecosystem. If you mess around getting nvim-dap to work then there's a chance things might change over the coming months and you might have to return to configuring it more often than you'd like. In this sense for now I'm happy just to open vscode or another more appropriate IDE to debug. But I can see myself using the plugins in a year or two when they've matured.
-
Is there any way to autocomplete language functions? For example, show things like fmt.Printf or fmt.Println when writing fmt.Print and pressing the autocomplete key.
Here are a few resources to get you started: 1. https://github.com/neovim/nvim-lspconfig 1. https://github.com/golang/tools/tree/master/gopls 1. https://github.com/williamboman/nvim-lsp-installer
-
rust_tools equivalent for C Sharp
Can recommend a combination of omnisharp-roslyn native LSP (installed manually or through something like mason or nvim-lsp-installer) with omnisharp-vim for some extra C#-niceties like OmniSharpRunTest, etc.
What are some alternatives?
code-settings-sync - 🌴💪 Synchronize your Visual Studio Code Settings Across Multiple Machines using GitHub GIST 💪🌴
nvim-lspconfig - Quickstart configs for Nvim LSP
dbatools - 🚀 SQL Server automation and instance migrations have never been safer, faster or freer
nvim-lspinstall - Provides the missing :LspInstall for nvim-lspconfig
PSScriptAnalyzer - Download ScriptAnalyzer from PowerShellGallery
omnisharp-vim - Vim omnicompletion (intellisense) and more for C#
vscode-powershell - Provides PowerShell language and debugging support for Visual Studio Code
mason-lspconfig.nvim - Extension to mason.nvim that makes it easier to use lspconfig with mason.nvim.
PSResourceGet - PSResourceGet is the package manager for PowerShell
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
nvim-jdtls - Extensions for the built-in LSP support in Neovim for eclipse.jdt.ls