nvim-lsp-installer
vscode-powershell
Our great sponsors
nvim-lsp-installer | vscode-powershell | |
---|---|---|
82 | 29 | |
2,022 | 1,649 | |
- | 1.1% | |
9.7 | 9.4 | |
over 1 year ago | 9 days ago | |
Lua | TypeScript | |
Apache License 2.0 | 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.
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.
vscode-powershell
-
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?
nvim-lspconfig - Quickstart configs for Nvim LSP
PSScriptAnalyzer - Download ScriptAnalyzer from PowerShellGallery
omnisharp-vim - Vim omnicompletion (intellisense) and more for C#
vetur - Vue tooling for VS Code.
nvim-lspinstall - Provides the missing :LspInstall for nvim-lspconfig
dbatools - 🚀 SQL Server automation and instance migrations have never been safer, faster or freer
mason-lspconfig.nvim - Extension to mason.nvim that makes it easier to use lspconfig with mason.nvim.
Open-Shell-Menu - Classic Shell Reborn.
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
notepad-plus-plus - Notepad++ official repository
nvim-jdtls - Extensions for the built-in LSP support in Neovim for eclipse.jdt.ls
PersistentWindows - fork of http://www.ninjacrab.com/persistent-windows/ with windows 10 update