LunarVim
rust-tools.nvim
Our great sponsors
LunarVim | rust-tools.nvim | |
---|---|---|
272 | 90 | |
17,421 | 2,165 | |
1.8% | - | |
7.6 | 0.0 | |
about 1 month ago | 4 months ago | |
Lua | Lua | |
GNU General Public License v3.0 only | 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.
LunarVim
-
Every Neovim, Every Config, All At Once
LunarVim
- LunarVIM: An IDE Layer for Neovim
-
Tools to achieve a 10x developer workflow on Windows
I would suggest to start getting into vim by first trying out popular vim keybinding plugins available on your favorite code editor and get used to those first. Then, if you want to dive deeper into the power of Neovim, try out popular configs like LazyVim, LunarVim, NvChad... Taking Neovim from a mere text editor to a full-featured IDE with features like intellisense, debugging, testing, etc... on your own takes quite a lot of work and configuration.
-
Helix 23.10 Highlights
I used Helix for a while due to its support for LSP out-of-the-box, which my Vim config at the time couldn't live up to. I switched back to NeoVim after finding LunarVim[1] which had everything I was trying to get setup in my own config.
- How to Transform Vim to a Complete IDE?
-
Mastering Emacs
I'll admit I didn't look into it, but Helix sounds like something like LunarVim (https://www.lunarvim.org/)
Personally I much prefer that the editor NOT ship with something like that by default, especially when it's so easy to set up. I have several different vim config I use, including a pretty bare-bones one for headless systems, and I much prefer the ability to customize something very specifically.
Build tools that can compose together, rather than a single do-it-all tool. That is the power of the low level editors vs IDE's.
- No inline errors in Python unless I add and delete a line
-
LazyVim
I can't comment on any implementation details, but at least with LunarVim (which I use for daily coding), a slowdown when interacting with LSP is very noticeable. Some others have attested to this on a GitHub issue.
I'm not doubting your experiences with the lack of a slowdown, but there is truth that others do experience it. That might be more of a problem with LunarVim itself rather than Vim, but how likely am I (as someone who would like to avoid what he calls "config hell") or other newcomers to avoid whatever pitfalls there are, if a distribution designed for ease of use by people who know better fall into them?
- Should Neovim now release a standard official configuration so that people who want an editor that just works out of the box get onboarded easily ?
-
neovim config
Anyways, although i have not used them, LazyVim and LunarVim comes highly recommended. You can try these and see what suits you .
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?
AstroNvim - AstroNvim is an aesthetic and feature-rich neovim config that is extensible and easy to use with a great set of plugins
NvChad - Blazing fast Neovim config providing solid defaults and a beautiful UI, enhancing your neovim experience.
SpaceVim - A community-driven modular vim/neovim distribution - The ultimate vimrc
helix - A post-modern modal text editor.
NvChad - An attempt to make neovim cli as functional as an IDE while being very beautiful , blazing fast. [Moved to: https://github.com/NvChad/NvChad]
nvim-cmp - A completion plugin for neovim coded in Lua.
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
Neovim-from-scratch - 📚 A Neovim config designed from scratch to be understandable
lsp_extensions.nvim - Repo to hold a bunch of info & extension callbacks for built-in LSP. Use at your own risk :wink:
LazyVim - Neovim config for the lazy
nvim-treesitter - Nvim Treesitter configurations and abstraction layer