formatter.nvim
nvim-cmp
formatter.nvim | nvim-cmp | |
---|---|---|
37 | 250 | |
1,284 | 7,109 | |
- | - | |
7.0 | 8.1 | |
7 days ago | 6 days ago | |
Lua | Lua | |
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.
formatter.nvim
-
null-ls will be archived
Can anyone explain why someone would use null-ls if you're using the modern lsp setup (say, from kickstart.nvim). I see comments mentioning formatting. I see formatters mentioned several times. Why not just use https://github.com/mhartington/formatter.nvim?
-
How to setup formatter for Python ???
I use null-ls (https://github.com/jose-elias-alvarez/null-ls.nvim), I haven't tried it for python, but haven't had trouble with lua, js, ts or rust. You can also look into formatter.nvim (https://github.com/mhartington/formatter.nvim).
-
Scalafmt and neovim
I use formatter.nvim for formatting
-
Does a language server replace ALE, syntastic, and the language plugin?
For formatting, formatter.nvim is a good choice and has similar setup to nvim-lint.
-
lsp.vim.buf.format parameters make tab indent 4 spaces
I finally installed this formatter plugin and configured it to execute de clang-format command like this
-
A Minimal Neovim Configuration for TypeScript Development featuring Lazy.nvim, LSP, Tree-Sitter, Prettier, Guess-Indent
mhartington/formatter.nvim is used for automatic code formatting. Its configuration also shows how to use nvim_create_augroup and nvim_create_autocmd from Lua.
-
Editing the same file in a split causes vim to jump to the top of the file when saving with autoformatter
This might have something to do with extmarks being clobbered when the new text is written. For example, here is a GitHub issue describing the problem: https://github.com/mhartington/formatter.nvim/issues/22 This is for formatter.nvim, but this would likely apply to any process that rewrites the whole buffer.
-
autoformat with lsp-zero
i have always had trouble with lsp formatting and null-ls (may just be me, i'm not super clued in) so i use formatter.nvim https://github.com/mhartington/formatter.nvim/
-
Neovim not formatting code correctly like VSCode does (prettier)
Take a look at formatter.nvim
-
How does vim.lsp.buf.format() deal with multiple attached LSP clients?
I've had really good experience with formatter-nvim.
nvim-cmp
-
What is this red color in cmp?
vim.api.nvim_set_hl(0, "PmenuSel", { bg = c.background_light, fg = "NONE" }) vim.api.nvim_set_hl(0, "Pmenu", { fg = c.foreground, bg = c.background_light }) vim.api.nvim_set_hl(0, "CmpItemAbbrDeprecated", { fg = c.foreground_light, bg = "NONE", strikethrough = true }) vim.api.nvim_set_hl(0, "CmpItemAbbrMatch", { fg = c.blue , bg = "NONE", bold = true }) vim.api.nvim_set_hl(0, "CmpItemAbbrMatchFuzzy", { fg = c.blue, bg = "NONE", bold = true }) vim.api.nvim_set_hl(0, "CmpItemMenu", { fg = c.purple, bg = "NONE", italic = true }) vim.api.nvim_set_hl(0, "CmpItemKindField", { fg = c.red }) vim.api.nvim_set_hl(0, "CmpItemKindProperty", { fg = c.red }) vim.api.nvim_set_hl(0, "CmpItemKindEvent", { fg = c.red }) vim.api.nvim_set_hl(0, "CmpItemKindText", { fg = c.green }) vim.api.nvim_set_hl(0, "CmpItemKindEnum", { fg = c.green }) vim.api.nvim_set_hl(0, "CmpItemKindKeyword", { fg = c.green }) vim.api.nvim_set_hl(0, "CmpItemKindConstant", { fg = c.yellow }) vim.api.nvim_set_hl(0, "CmpItemKindConstructor", { fg = c.yellow }) vim.api.nvim_set_hl(0, "CmpItemKindReference", { fg = c.yellow }) vim.api.nvim_set_hl(0, "CmpItemKindFunction", { fg = c.purple }) vim.api.nvim_set_hl(0, "CmpItemKindStruct", { fg = c.purple }) vim.api.nvim_set_hl(0, "CmpItemKindClass", { fg = c.purple }) vim.api.nvim_set_hl(0, "CmpItemKindModule", { fg = c.purple }) vim.api.nvim_set_hl(0, "CmpItemKindOperator", { fg = c.purple }) vim.api.nvim_set_hl(0, "CmpItemKindVariable", { fg = c.foreground }) vim.api.nvim_set_hl(0, "CmpItemKindFile", { fg = c.foreground }) vim.api.nvim_set_hl(0, "CmpItemKindUnit", { fg = c.orange }) vim.api.nvim_set_hl(0, "CmpItemKindSnippet", { fg = c.orange }) vim.api.nvim_set_hl(0, "CmpItemKindFolder", { fg = c.orange }) vim.api.nvim_set_hl(0, "CmpItemKindMethod", { fg = c.blue }) vim.api.nvim_set_hl(0, "CmpItemKindValue", { fg = c.blue }) vim.api.nvim_set_hl(0, "CmpItemKindEnumMember", { fg = c.blue }) vim.api.nvim_set_hl(0, "CmpItemKindInterface", { fg = c.aqua }) vim.api.nvim_set_hl(0, "CmpItemKindColor", { fg = c.aqua }) vim.api.nvim_set_hl(0, "CmpItemKindTypeParameter", { fg = c.aqua }) -- https://github.com/hrsh7th/nvim-cmp/pull/1689 vim.api.nvim_set_hl(0, 'FloatBorder', { fg = c.background_light, bg = c.background_light })
-
cmp border background is changed all of a sudden.
Doing a fast scan on the commit history this is probably related to https://github.com/hrsh7th/nvim-cmp/pull/1689 . Hope it helps.
-
Do I need NeoVIM?
https://github.com/hrsh7th/nvim-cmp This is an autocompletion engine https://github.com/nvim-treesitter/nvim-treesitter This allows NeoVim to install parsing scripts so NeoVim can do things like code highlighting. https://github.com/williamboman/mason.nvim Not strictly necessary, but allows you to access a repo of LSP, install them, and configure them for without you actively messing about in config files. https://github.com/neovim/nvim-lspconfig Also not strictly necessary, but vastly simplifies LSP setup. https://github.com/williamboman/mason-lspconfig.nvim This lets the above two plugins talk to each other more easily.
-
Can't go down when writing a command nvim
Edit: Solved I only had to do this
-
What is your most anticipated PR?
toggling sources by Treesitter context
-
About some deprecations in Neovim core
But today I'm a different person, and I'm sure that this is the right decision. I already gave a spiel on the cmp PR, but lemme copy-paste my response for those that weren't following the issue or don't check their GitHub notifications:
-
nvim starts multiple node processes leading to very high memory usage
EDIT: I was able to reproduce the issue with a simplified nvim-cmp init.vim - posted here: https://github.com/hrsh7th/nvim-cmp/issues/1728
-
[Need Help]: I am having trouble getting autocomplete with clangd.
You need to add nvim-cmp and cmp-nvim-lsp
-
is it possible to limit the size of nvim-cmps autocompletion window?
one thing that always annoyed me is how the autocomplete window behaves. when the space below your current line isn't sufficient it just teleports above the line. i know you can set a custom menu direction but i'd much rather have it pop up in a consistent place that is below the current line. the other behavior i dislike is the sizing. it's as big as the longest function in the list which can make the window enormous, to the point where there's almost no place left for the docs window. there aren't really any docs in the example below but i imagine with the little space that is left it'll get troublesome for more verbose docs such as with rust. i'd like to somehow tell nvim-cmp to always pop up below the current line, no matter how long the list is and possibly limit the horizontal size. is that at all possible? i've looked through the nvim-cmp wiki but haven't found an adequate solution. does this go beyond nvim-cmp?
-
Toggling the nvim-cmp documentation window
Update: This isn't currently supported by nvim-cmp (and in fact it has been a feature request for a bit) and so I did my best and opened a PR that implements it :)
What are some alternatives?
null-ls.nvim - Use Neovim as a language server to inject LSP diagnostics, code actions, and more via Lua.
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
neoformat - :sparkles: A (Neo)vim plugin for formatting code.
cmp-nvim-lsp - nvim-cmp source for neovim builtin LSP client
format.nvim - A wrapper around Neovims native LSP formatting. [Moved to: https://github.com/lukas-reineke/lsp-format.nvim]
coq.artifacts
vim-clang-format - Vim plugin for clang-format, a formatter for C, C++, Obj-C, Java, JavaScript, and so on.
completion-nvim - A async completion framework aims to provide completion to neovim's built in LSP written in Lua
vim-autoformat - Provide easy code formatting in Vim by integrating existing code formatters.
LuaSnip - Snippet Engine for Neovim written in Lua.
efm-langserver - General purpose Language Server
rust-tools.nvim - Tools for better development in rust using neovim's builtin lsp