null-ls.nvim
lsp-format.nvim

null-ls.nvim | lsp-format.nvim | |
---|---|---|
165 | 16 | |
3,554 | 585 | |
- | 0.7% | |
0.0 | 5.1 | |
over 1 year ago | 6 months ago | |
Lua | Lua | |
GNU General Public License v3.0 or later | - |
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.
null-ls.nvim
-
[SOLVED] Vue 3 + TypeScript + Inlay Hint support in NeoVim
I'd almost given up on finding "the right" solution. Everywhere I looked, others had "solved" the issue in different ways: they were using the vtsls TypeScript LSP wrapper instead of ts_ls, or they were using coc.nvim, or the now-archived null-ls.nvim. But nowhere could I simply find a reliable configuration for a Vue language server configured natively in NeoVim.
- cpp setting problem
-
Being a bash developer in the 21st century
you can use nvim then, it has shellcheck for diagnostics and formatting, like in vscode :)
here the link to the config: https://github.com/jose-elias-alvarez/null-ls.nvim/blob/main...
-
Linting/formatting and LSP
I use a lot of different languages generally and I'm running into issues around formatting. Is there any standard way to use LSP formatting by default and otherwise fallback to specific linter/formatting programs? I believe null-ls is the normal way of dealing with this, but since it's been archived, I'd rather not rely on it.
-
How to setup efm-langserver for pint formatter?
I've been using pint for formatting php files with null-ls.nvim. Few days ago null-ls.nvim has announced that the plugin will be archived in few months so I started migrating all my formatters and linter from null-ls to efm-langserver. I got other things such as prettier, black, isort, mypy, etc. working but can't get pint to work with php files: If I run pint via efm-langserver, everything is deleted from the buffer, and the saved file is formatted separately. How do I setup efm-langserver correctly to work with pint? Below is my config.yml for pint currently. yaml tools: pint: &pint format-command: "pint --no-interaction --quiet ${INPUT}" format-stdin: false languages: php: - <<: *pint Thank you.
- Archiving Null-Ls
- null-ls will be archived
-
Why is nobody using CoC anymore?
Because null-ls.nvim & mason.nvim together do everything I wanted CoC for
- Your favourite Neovim plugins?
lsp-format.nvim
-
My Setup for Responsive (Immutable) Formatting
suffice it to say, I haven't needed to mess with it in a very long time, and it works very nicely and smoothly. I based it on https://github.com/lukas-reineke/lsp-format.nvim back before he extracted that plugin from his dotfiles, but over time I added a lot.
- Delay when formatting on save
-
Cursor moves on format
Ok guys I solved it by using this wonderful plugin https://github.com/lukas-reineke/lsp-format.nvim . Apparently it had something to do with setting up my autosave from null-ls but can't be sure. Anyways, solved.
-
Format on Save
My first reaction is to set a buffer-exclusive autocmd on lsp attach to call vim.lsp.buf.format(), that should work if you don't want depdenencies. Another way to go is https://github.com/lukas-reineke/lsp-format.nvim, it's a thin wrapper around nvim's format and can provide format on save.
-
How to turn off on-save formatting in null-ls and let Lsp prettier and Eslint format instead? [LazyVim]
Use lsp-format.nvim and put null-ls on the blacklist.
-
Scalafmt and neovim
If you already use metals as a language server, it looks like scalafmt support is already built in. If you're using metals in Neovim but not getting formatting, check your lsp configuration. Alternatively, use lsp-format.nvim to ensure formatting happens. That goes for using it with null-ls, too.
-
Am I interweaving lspconfig and lsp-zero correctly?
Thanks! One additional question, I'm using lsp-format. And to use it, I just
-
Slow formatters end up overwriting changes since last save, any ideas how to change this behavior?
My plugin lukas-reineke/lsp-format.nvim does that. It wraps around the built-in LSP formatting with a couple opinionated improvements.
-
Autoformatting on save with vim.lsp.buf.format() and BufWritePre
You can take a look at my plugin LSP-format.nvim for a bit more robust solution to async format on save. But it will also write the file twice. There is currently no other way to do this.
-
null-ls & terraformls format on save prompt
I recommend instead using lsp-format.nvim to manage multiple LSP clients trying to format.
What are some alternatives?
lsp-zero.nvim - A starting point to setup some lsp related features in neovim.
formatter.nvim
nvim-lint - An asynchronous linter plugin for Neovim complementary to the built-in Language Server Protocol support.
nvim-conf - ☄ Maddison's Neovim configuration!
nvim-lspconfig - Quickstart configs for Nvim LSP
vim-python-pep8-indent - A nicer Python indentation style for vim.
nvoid - nvim with lua is cool
mason.nvim - Portable package manager for Neovim that runs everywhere Neovim runs. Easily install and manage LSP servers, DAP servers, linters, and formatters.
vscode-langservers-extracted - vscode-langservers bin collection.
volar - ⚡ Explore high-performance tooling for Vue [Moved to: https://github.com/vuejs/language-tools]
packspec - ALPHA package dependencies spec
