kakoune-lsp
nvim-cmp
kakoune-lsp | nvim-cmp | |
---|---|---|
9 | 250 | |
575 | 7,154 | |
0.5% | - | |
9.3 | 8.1 | |
5 days ago | 1 day ago | |
Rust | Lua | |
The Unlicense | 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.
kakoune-lsp
-
Which editor do you use for your Go coding?
Kakoune with LSP (gopls).
- kak-lsp release 11.1.0
-
Kakoune + Julia
You could dive into installing kak-lsp, which will provide the code intelligence features you want. Kakoune doesn't do windowing on it's own, so your going to need to rely on something like tmux or a terminal emulator that does similar, such as wezterm, or even a tiling window manager (which is what is being used in the video). Kakoune really needs a lot of time invested to configure well though.
-
Massive preludes: why?
Why do you need vscode? Kakoune supports code actions, so this should work in the editor with the best editing model ever. See lsp-code-actions from https://github.com/kak-lsp/kak-lsp.
-
Is kakoune more lightweight than vim or minimal? Why kakoune and not vim in your opinion?
In addition, rather than using its own full-fledged programming language for plugins or choosing to use a specific programming language, it provides a limited configuration language that's closer to a domain-specific language and to be used as a "glue" between Kakoune and programs written in any language. For example, the kak-lsp plugin uses a program written in Rust that is integrated with Kakoune with a thin wrapper of Kakoune's configuration language.
-
kak-lsp and godot engine
If you're having problems with these capabilities, try to look at the kak-lsp debug output: https://github.com/kak-lsp/kak-lsp#troubleshooting
-
kak-lsp + terraform-ls
kak-lsp doesn't print to *debug* under normal operation. If you want to check on kak-lsp, enable verbose logging as described here and tail -f the log file.
-
Currently looking for something other than vim and emacs. I have some questions for kakoune.
So, since pretty much everything happens through a shell, you can use anything that produces an executable to write your logic. kak-lsp, for example, is written in Rust, with some kakscript to define the commands, hooks and options a user needs to interface with it.
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?
gdscript.kak - GDScript syntax highlighting for Kakoune
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
kakoune-doas-write - Fork of kakoune-sudo-write to use doas instead.
cmp-nvim-lsp - nvim-cmp source for neovim builtin LSP client
tower-lsp - Language Server Protocol implementation written in Rust
coq.artifacts
age-plugin-yubikey - YubiKey plugin for age
completion-nvim - A async completion framework aims to provide completion to neovim's built in LSP written in Lua
cargo-limit - Productivity improvements for Rust ecosystem: warnings are skipped until errors are fixed, LSP-independent Neovim integration, etc.
LuaSnip - Snippet Engine for Neovim written in Lua.
nih-plug - Rust VST3 and CLAP plugin framework and plugins - because everything is better when you do it yourself
rust-tools.nvim - Tools for better development in rust using neovim's builtin lsp