crates.nvim
rust-tools.nvim
crates.nvim | rust-tools.nvim | |
---|---|---|
1 | 90 | |
11 | 2,165 | |
- | - | |
5.0 | 0.0 | |
almost 2 years ago | 4 months ago | |
Lua | Lua | |
- | 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.
crates.nvim
-
crates.nvim - a helper for managing crates.io versions
Ha-ha, what a funny coincidence! I've recently started working on plugin with same idea too. Love your approach to make user configurate everything!
rust-tools.nvim
-
[Experimental] Auto find Rust executables for DAP | Linux
This is not a robust solution to the problem. I haven't worked on a large Rust project, so I do not know if this is valid for all kinds of Rust projects. Maybe there is a better debugging config setups/plugins out there (simrat39/rust-tools.nvim is one from what I have searched for). I plan to keep using this config, till it breaks; and try and fix it when it does.
-
NeoVim IDE setup
rust-tools is what I'm currently using, https://github.com/simrat39/rust-tools.nvim
-
What editor are you using for Rust?
I then took the snippet from, I also changed the path to the correct install path of the above. https://github.com/simrat39/rust-tools.nvim/wiki/Debugging
-
Neovim & Rust
rust-tools.nvim and crates.nvim should be helpful for you. :)
-
What's your current Vim+Rust setup?
I'd start with nvim-treesitter, nvim-lspconfig, and use rust-tools.nvim as an accelerant. Any remaining advice I'd have is about Neovim but not about Rust. That advice would also be mostly questions of taste for this-or-that decisions.
-
Refactoring
Are you using https://github.com/simrat39/rust-tools.nvim/ ?
-
Rust + Neovim setup gotcha
TIL that if you install Rust via Homebrew (like brew install rust), auto formatting (or more specifically, lsp formatting) doesn't work properly. I used both Rust Analyzer and rust-tools) to setup rust lsp and configured it with tons of options, thinking maybe something will work but somehow, one thing never did - auto formatting. This is the command I use for setting up auto formatting via lsp:
-
What setup do you use to program in rust?
neovim + native lsp with rust-tools.nvim, running nixos so I use flakes for my dev environments
- [Neovim] Rust-tools.nvim: outils pour des fonctionnalités supplémentaires sur Rust Analyzer
-
NVim, Rust, LSP (rust-analyzer + rust-tools) issue
I opened an issue https://github.com/simrat39/rust-tools.nvim/issues/369 after searching for such behavior in existing ones. But I also ask here in case it's a known problem.
What are some alternatives?
nvim-cmp - A completion plugin for neovim coded in Lua.
NvChad - Blazing fast Neovim config providing solid defaults and a beautiful UI, enhancing your neovim experience.
crates.nvim - A neovim plugin that helps managing crates.io dependencies
LunarVim - 🌙 LunarVim is an IDE layer for Neovim. Completely free and community driven.
vim-crates - Handle Cargo dependencies like a Rustavimean.
helix - A post-modern modal text editor.
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
lsp_extensions.nvim - Repo to hold a bunch of info & extension callbacks for built-in LSP. Use at your own risk :wink:
nvim-treesitter - Nvim Treesitter configurations and abstraction layer
lsp-status.nvim - Utility functions for getting diagnostic status and progress messages from LSP servers, for use in the Neovim statusline
neovim - Vim-fork focused on extensibility and usability