rust-tools.nvim
null-ls.nvim
rust-tools.nvim | null-ls.nvim | |
---|---|---|
90 | 164 | |
2,165 | 3,554 | |
- | - | |
0.0 | 0.0 | |
4 months ago | 9 months ago | |
Lua | Lua | |
MIT License | 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.
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.
null-ls.nvim
- cpp setting problem
-
Being a bash developer in the 21st century
you can use nvim then, it has shellcheck for diagnostics and formatting, like in vscode :)
here the link to the config: https://github.com/jose-elias-alvarez/null-ls.nvim/blob/main...
-
Linting/formatting and LSP
I use a lot of different languages generally and I'm running into issues around formatting. Is there any standard way to use LSP formatting by default and otherwise fallback to specific linter/formatting programs? I believe null-ls is the normal way of dealing with this, but since it's been archived, I'd rather not rely on it.
-
How to setup efm-langserver for pint formatter?
I've been using pint for formatting php files with null-ls.nvim. Few days ago null-ls.nvim has announced that the plugin will be archived in few months so I started migrating all my formatters and linter from null-ls to efm-langserver. I got other things such as prettier, black, isort, mypy, etc. working but can't get pint to work with php files: If I run pint via efm-langserver, everything is deleted from the buffer, and the saved file is formatted separately. How do I setup efm-langserver correctly to work with pint? Below is my config.yml for pint currently. yaml tools: pint: &pint format-command: "pint --no-interaction --quiet ${INPUT}" format-stdin: false languages: php: - <<: *pint Thank you.
- Archiving Null-Ls
- null-ls will be archived
-
Why is nobody using CoC anymore?
Because null-ls.nvim & mason.nvim together do everything I wanted CoC for
- Your favourite Neovim plugins?
-
How can I get yapf, black, and other formatters working with pylsp?
There is a good answer. I think you know lua and neovim config enough to pick things that you need. If you need a short answer, null-ls is the way.
What are some alternatives?
NvChad - Blazing fast Neovim config providing solid defaults and a beautiful UI, enhancing your neovim experience.
formatter.nvim
LunarVim - 🌙 LunarVim is an IDE layer for Neovim. Completely free and community driven.
nvim-lspconfig - Quickstart configs for Nvim LSP
helix - A post-modern modal text editor.
neoformat - :sparkles: A (Neo)vim plugin for formatting code.
nvim-cmp - A completion plugin for neovim coded in Lua.
StyLua - An opinionated Lua code formatter
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
nvim-lint - An asynchronous linter plugin for Neovim complementary to the built-in Language Server Protocol support.
lsp_extensions.nvim - Repo to hold a bunch of info & extension callbacks for built-in LSP. Use at your own risk :wink:
efm-langserver - General purpose Language Server