dotfiles
rust.vim
dotfiles | rust.vim | |
---|---|---|
25 | 23 | |
58 | 3,797 | |
- | 0.7% | |
8.4 | 0.0 | |
19 days ago | about 1 month ago | |
Shell | Vim Script | |
- | Apache License 2.0 |
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.
dotfiles
-
Can anyone recommend a good github dotfiles repos for neovim that uses LazyVim as it's plugin manager?
https://github.com/Integralist/dotfiles (.config/nvim is a submodule to https://github.com/Integralist/nvim)
- Snippets folder for LuaSnip
- LuaSnip + vim-go
- Help with nvim-cmp and luasnip
-
Do you want a faster way to create Lua Snippets?
I could imagine that 'project' or 'domain' specific snippets created on-the-fly when needed could be a popular idea because it's often I'm working on something and suddenly think "yeah this would be good as a snippet" and then I look at... https://github.com/Integralist/dotfiles/blob/main/.snippets/go.lua ...and then I inevitably say to myself "f*** it, I'll do it later".
- do you have gcc mapped to some shortcut? if so, what? I find I use it all the time so 3 keypresses does not seem efficient when use is so frequent
- I refactored my lua structure and have lost some UI styling ?
- My status bar randomly disappears?
-
rust-analyzer autocmd error AND custom nvim-lint error with cargo check
I have both https://github.com/simrat39/rust-tools.nvim and https://github.com/mfussenegger/nvim-lint configured and I started noticing something that was working before had suddenly become broken, and it's not clear what changes I've made to my config (https://github.com/Integralist/dotfiles/tree/main/.config/nvim) that would have caused this error.
-
cmp is showing every possible suggestion for all LSPs?
My config can be found here: https://github.com/Integralist/dotfiles/tree/main/.config/nvim
rust.vim
-
How to prevent rust-analyzer (rust lsp) from checking code on each save
I am using rustaceanvim and rust.vim.
-
Issue with syntax highlighting in rust with rust-analyzer
When the file first loads, it uses the syntax defined in the $VIMRUNTIME/syntax/rust.vim file from rust.vim, which is what I want, but after a few seconds (probably once rust-analyzer loads and runs), it changes the highlighting to use different colours (there's probably a better way to describe it, but a video is easier to show). This colour change also happens when I write the file (and rust-analyzer runs again).
-
Can’t run specific test via LSP
Or this https://github.com/rust-lang/rust.vim, it has example with running tests
-
Struggling to get basic diagnostic working with LSP
If you need basic syntax checking on leaving insert mode (without saving file), https://github.com/rust-lang/rust.vim can be used
-
Is it possible to have Rust doc test comments highlighted in Neovim?
Seems like there's a tree-sitter solution, but I do want to note that this works out of the box with rust.vim: https://github.com/rust-lang/rust.vim/issues/63. It might be the built-in Rust support is out of date -- using that repo as a plugin would do the trick.
-
Default mappings override user mappings in Rust ( [[ and ]] mappings )
Most of the customizations in the $VIMRUNTIME's rust ftplugin are guarded behind a flag (g:rust_fold, g:rustfmt_autosave,g:rust_recommended_style, etc.) to control enabling and disabling them, but for some reason the navigation mappings are unconditionally defined, with no flag to turn them off... It might be worth going through the issues in https://github.com/rust-lang/rust.vim to see if that ever came up before.
-
Config For rust dev
Is having rust.vim necessary if I'm using rust-tools already?
-
Need help for setting up neovim.
Primeagen has a series, you could also try spacevim or lunarvim( i prefer lunarvim). If you want to read the docs and setup yourself 1. lsp and code completion mentioned in #5. 2. treesitter 3. lsp handles that, you have to install java's lsp, this improves its look. 4. Make your own remaps, some languages have a plugin for this but i can't find one for java, this is the one for rust. 5. Install cmp and one of the snippet engines.
-
Rust with Vim
writing rust is the same regardless of which editor you use and using vim is the same regardless of what programming language you are in, so i dont think you need a tutorial neccissarily. ive been using this plugin for rust-specific features https://github.com/rust-lang/rust.vim
-
Configure NeoVim for Rust Dev
As for plugins for Rust development, I’d recommend Conquer of Completion (using the coc-rust-analyser coc plugin), Rust lang’s rust plugin, and the Toml plugin
What are some alternatives?
mason-lspconfig.nvim - Extension to mason.nvim that makes it easier to use lspconfig with mason.nvim.
Clippy - A bunch of lints to catch common mistakes and improve your Rust code. Book: https://doc.rust-lang.org/clippy/
nvim - A non-minimal Neovim config built to work most efficiently with Frontend Development
coc-rust-analyzer - rust-analyzer extension for coc.nvim
sauce - A tool to help manage context/project specific shell-things like environment variables.
doom-emacs - An Emacs framework for the stubborn martian hacker [Moved to: https://github.com/doomemacs/doomemacs]
.dotfiles - my dotfiles over the years
YouCompleteMe - A code-completion engine for Vim
neovim-rust - Sample neovim and vim configurations for Rust development
Rustlings - :crab: Small exercises to get you used to reading and writing Rust code!
nvim - Neovim configuration
refactoring.nvim - The Refactoring library based off the Refactoring book by Martin Fowler