kakoune-lsp
Rust Language Server
kakoune-lsp | Rust Language Server | |
---|---|---|
9 | 6 | |
575 | 3,568 | |
0.5% | - | |
9.3 | 7.0 | |
4 days ago | over 1 year ago | |
Rust | Rust | |
The Unlicense | GNU General Public License v3.0 or later |
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.
Rust Language Server
-
Why doesn't rust-analyzer reuse infrastructures of rustc?
In the last there was RLS that did exactly that. But the approach of rust-analyzer was found to be more performant.
-
[RFC] Generate Cabal files from TOML
LSP support seems to be lacking as well, at least rust doesn't seem to have Cargo.toml support? https://github.com/rust-lang/rls/issues/785
-
Referencing files in subfolders and difference between borrowing and C like references
apparently, it means that you're using the old RLS-based Rust plugin for VS Code, rather than the rust-analyzer plugin. You probably won't see a lot of people familiar with RLS's error messages.
-
friendly reminder for our vscode folks, use rust-analyzer
Why: The rust-analyzer extension integrates with rust-analyzer, an alternative language server for Rust. rust-analyzer tends to perform better and get less confused with your code as compared to RLS, which the Rust extension uses.
-
Show HN: Skruv – No-dependency, no-build, small JavaScript framework
I have tried writing websites with rust instead of JavaScript. Unfortunately, the tooling is just not there. More specifically, I am talking about wasm-bindgen, which provides two-way bindings. The problem with it is that since all the declarations are generated with build.rs, there is no autocompletion. Since I am spoiled by modern tooling, no autocompletion to me means not feasible pass demo stage. (https://github.com/rust-lang/rls/issues/1489)
Aside from the lack of autocompletion, passing rust closures to js land (DOM) is extremely janky as well. However, that might be caused by my lack of experience with rust.
(If you are curious, this is what I made: https://github.com/SCLeoX/non-grid-path-finder)
-
José Valim The Creator Of The Elixir Programming
Python the core devs don't care about tooling and they have IDE's, Java is an enterprise monolith so IDE's are the standard, Rust yes it is (https://github.com/rust-lang/rls), Elm I have no idea I don't use it.
What are some alternatives?
gdscript.kak - GDScript syntax highlighting for Kakoune
Rustup - The Rust toolchain installer
kakoune-doas-write - Fork of kakoune-sudo-write to use doas instead.
Racer - Rust Code Completion utility
tower-lsp - Language Server Protocol implementation written in Rust
rusty-tags - Create ctags/etags for a cargo project
age-plugin-yubikey - YubiKey plugin for age
rust-analyzer - A Rust compiler front-end for IDEs
cargo-limit - Productivity improvements for Rust ecosystem: warnings are skipped until errors are fixed, LSP-independent Neovim integration, etc.
semantic-rs
nih-plug - Rust VST3 and CLAP plugin framework and plugins - because everything is better when you do it yourself
Clippy - A bunch of lints to catch common mistakes and improve your Rust code. Book: https://doc.rust-lang.org/clippy/