gopher.nvim
kakoune-lsp
gopher.nvim | kakoune-lsp | |
---|---|---|
6 | 9 | |
267 | 575 | |
- | 0.5% | |
2.1 | 9.3 | |
18 days ago | 3 days ago | |
Lua | Rust | |
- | The Unlicense |
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.
gopher.nvim
-
Neovim + Golang Set up
You can configure gopls by this guide. How about go.nvim I don't know, but you can install gopher.nvim(which I'm author) and its will work after install without any configurations
-
Updates of gopher.nvim
I pushed a little changes to gopher.nvim: - Comment generator - if err != nil generator - Add setuping support
-
What are the best vim plugins for Go right now?
I use nvim + native lsp(with gopls) + gopher.nvim
-
Update of gopher.nvim, the plugin for making go development easiest
Some time ago. I posted about [gopher.nvim](https://github.com/olexsmir/gopher.nvim).
-
Which editor do you use for your Go coding?
Neovim + lsp(gopls) + gopher.nvim plugin
-
[gopher.nvim] Plugin for golang development
Github
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.
What are some alternatives?
nvim-go - A minimal implementation of Golang development plugin for Neovim
gdscript.kak - GDScript syntax highlighting for Kakoune
rayso.nvim - A simple neovim plugin that enables you to instantly create snippets on ray.so
kakoune-doas-write - Fork of kakoune-sudo-write to use doas instead.
lsp-inlayhints.nvim
tower-lsp - Language Server Protocol implementation written in Rust
vim-go - Go development plugin for Vim
age-plugin-yubikey - YubiKey plugin for age
go.nvim - A feature-rich Go development plugin, leveraging gopls, treesitter AST, Dap, and various Go tools to enhance the dev experience.
cargo-limit - Productivity improvements for Rust ecosystem: warnings are skipped until errors are fixed, LSP-independent Neovim integration, etc.
ltex_extra.nvim - Provides external LTeX file handling (off-spec lsp) and other functions.
nih-plug - Rust VST3 and CLAP plugin framework and plugins - because everything is better when you do it yourself