Launch.nvim
nvim-cmp
Launch.nvim | nvim-cmp | |
---|---|---|
52 | 250 | |
1,951 | 7,154 | |
1.1% | - | |
7.3 | 8.1 | |
19 days ago | 2 days ago | |
Lua | Lua | |
GNU General Public License v3.0 only | 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.
Launch.nvim
-
Add rust.vim autoformat in nvim basic ide
Hi, everyone! I'm new at neovim and this week I'm trying to build my own config, instead of nvchad which is really cool too. Now I'm using nvim basic ide and I just can't config the rust.vim autoformat as I did in nvchad. Can someone help me pls? Edit: This is my rustvim.lua content:
-
LazyVim
100% and I dislike having two vim configurations to maintain which is why they also have https://github.com/LunarVim/nvim-basic-ide
With LazyVim I basically got rid of the both, and now my vim config is literally a few overrides https://www.lazyvim.org/configuration/general that are not distribution specific at all.
-
I somehow messed up some icons in iterm2 with neovim for gitsigns and unsure how to fix
I use this as my base configuration for neovim and I don't have any differences that I can see regarding gitsigns. When I delete something rather than showing the icon I used to have, it shows the character used in the config file.
-
Not able to get LSP keybinds to work for rust while using nvim-basic-ide
Hi there. I'm switching from another editor to nvim and decided to use https://github.com/LunarVim/nvim-basic-ide as a starting point of my configuration.
-
seeking advice on various neovim configs
i use basic ide for starting point lua config and tweak it
-
How are you supposed to upgrade neovim? Every existing plugin I have just breaks and I don't have the time/skill/knowledge to rebuild everything.
You may also need to audit your plugins. I found that a handful of plugins I was using between .7 and .8 got deprecated and I had to find replacements. It actually did lead me to completely redoing my setup, but I was able to use this basic setup as a template since it largely matched a lot of my config.
-
Volar with VueJS 3
I'm trying to use Volar https://github.com/vuejs/language-tools in a project created with create-vue https://github.com/vuejs/create-vue. My config is forked from https://github.com/LunarVim/nvim-basic-ide and Volar is installed with Mason (having previously installed the Vue lang server).
-
Is it safe/recommended to make edits for depreciated vim.treesitter.query.get?
Won't they get updated/edited by further updates? I am using the config from https://github.com/LunarVim/nvim-basic-ide
-
Neovim Native LSP with Tailwind CSS is Extremely Buggy and Slow
Update: - I think the issue that was causing the tailwind lsp to be slow was related to the fact that I was using lsp-zero config to manage my lsp. - It's possible that lsp-zero config was using some settings that were making it slow, but I'm not entirely sure. As a result, I decided to abandon lsp-zero config and create my own config to manage lsp. - My new config is based on the nvim-basic-ide config. You can take a look at my new config here. - Now everything is working fine.
-
what is the nvim lsp equivalent to ale's :ALEFix ?
I am using this as a base which caused the confusion for me: https://github.com/LunarVim/nvim-basic-ide/blob/master/lua/user/lsp/null-ls.lua
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?
noice.nvim - 💥 Highly experimental plugin that completely replaces the UI for messages, cmdline and the popupmenu.
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
Neovim-from-scratch - 📚 A Neovim config designed from scratch to be understandable
cmp-nvim-lsp - nvim-cmp source for neovim builtin LSP client
kickstart.nvim - A launch point for your personal nvim configuration
coq.artifacts
LunarVim - 🌙 LunarVim is an IDE layer for Neovim. Completely free and community driven.
completion-nvim - A async completion framework aims to provide completion to neovim's built in LSP written in Lua
AstroNvim - AstroNvim is an aesthetic and feature-rich neovim config that is extensible and easy to use with a great set of plugins
LuaSnip - Snippet Engine for Neovim written in Lua.
pulsar - A Community-led Hyper-Hackable Text Editor
rust-tools.nvim - Tools for better development in rust using neovim's builtin lsp