cargo-limit
kakoune-lsp
Our great sponsors
cargo-limit | kakoune-lsp | |
---|---|---|
6 | 9 | |
240 | 573 | |
1.3% | 1.7% | |
7.4 | 9.3 | |
16 days ago | 6 days ago | |
Rust | Rust | |
Apache License 2.0 | 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.
cargo-limit
- Cargo-limit: Cargo with less noise: warnings are skipped until errors are fixed
- cargo-limit 0.0.10
-
What's everyone working on this week (38/2022)?
Both neovim-remote and nvim-send are no longer needed for the project, because Neovim >= 0.7.0 now has nvim --remote-send. Since it's not high priority and it's trivial enough to change, I left an issue for anyone who wants to contribute to the project.
- cargo-limit 0.0.9: Automatically jump to Rust compilation errors/warnings in Neovim
- cargo-limit 0.0.9: Automatically jump to compilation errors/warnings in Neovim
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?
alexandrie - An alternative crate registry, implemented in Rust.
gdscript.kak - GDScript syntax highlighting for Kakoune
nextest - A next-generation test runner for Rust.
kakoune-doas-write - Fork of kakoune-sudo-write to use doas instead.
nih-plug - Rust VST3 and CLAP plugin framework and plugins - because everything is better when you do it yourself
tower-lsp - Language Server Protocol implementation written in Rust
pacaptr - Pacman-like syntax wrapper for many package managers.
age-plugin-yubikey - YubiKey plugin for age
cargo-about - 📜 Cargo plugin to generate list of all licenses for a crate 🦀
nvim-completion - :zap: An async autocompletion framework for Neovim
Rust Language Server - Repository for the Rust Language Server (aka RLS)