rust-analyzer
vim-lsp-settings
Our great sponsors
rust-analyzer | vim-lsp-settings | |
---|---|---|
207 | 24 | |
9,320 | 1,231 | |
- | - | |
10.0 | 8.3 | |
about 2 years ago | 9 days ago | |
Rust | Vim Script | |
GNU General Public License v3.0 or later | 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.
rust-analyzer
-
rust-analyzer changelog #177
#14561 map tokens from include! expansion to the included file
-
Make LSP-Rust-analyzer works
return { tools = { -- autoSetHints = false, on_initialized = function() vim.api.nvim_create_autocmd({ "BufWritePost", "BufEnter", "CursorHold", "InsertLeave" }, { pattern = { "*.rs" }, callback = function() vim.lsp.codelens.refresh() end, }) end, auto = false, inlay_hints = { -- Only show inlay hints for the current line only_current_line = false, auto = false, -- Event which triggers a refersh of the inlay hints. -- You can make this "CursorMoved" or "CursorMoved,CursorMovedI" but -- not that this may cause higher CPU usage. -- This option is only respected when only_current_line and -- autoSetHints both are true. only_current_line_autocmd = "CursorHold", -- whether to show parameter hints with the inlay hints or not -- default: true show_parameter_hints = false, -- whether to show variable name before type hints with the inlay hints or not -- default: false show_variable_name = false, -- prefix for parameter hints -- default: "<-" -- parameter_hints_prefix = "<- ", parameter_hints_prefix = " ", -- prefix for all the other hints (type, chaining) -- default: "=>" -- other_hints_prefix = "=> ", other_hints_prefix = " ", -- whether to align to the lenght of the longest line in the file max_len_align = false, -- padding from the left if max_len_align is true max_len_align_padding = 1, -- whether to align to the extreme right or not right_align = false, -- padding from the right if right_align is true right_align_padding = 7, -- The color of the hints highlight = "Comment", }, hover_actions = { auto_focus = false, border = "rounded", width = 60, -- height = 30, }, }, server = { --[[ $ mkdir -p ~/.local/bin $ curl -L https://github.com/rust-analyzer/rust-analyzer/releases/latest/download/rust-analyzer-x86_64-unknown-linux-gnu.gz | gunzip -c - > ~/.local/bin/rust-analyzer $ chmod +x ~/.local/bin/rust-analyzer --]] -- cmd = { os.getenv "HOME" .. "/.local/bin/rust-analyzer" }, cmd = { os.getenv "HOME" .. "~/.cargo/bin/rust-analyzer" }, on_attach = require("user.lsp.handlers").on_attach, capabilities = require("user.lsp.handlers").capabilities, settings = { ["rust-analyzer"] = { lens = { enable = true, }, checkOnSave = { command = "clippy", }, }, }, }, }
-
rust-analyzer changelog #164
I would like changes like https://github.com/rust-analyzer/rust-analyzer/pull/13799 to be listed in 'Breaking Changes' category, to приманка draw the users' attention.
-
Mun v0.4.0 released
For those of you who haven’t heard of Mun before, Mun is an embeddable programming language empowering creation through iteration. The idea to create Mun originated out of frustration with the Lua dynamic scripting language and a desire to have similar hot reloading functionality available in Rust. As such, it’s not a direct competitor with Rust, but instead is intended to be used with Rust (or C/C++) as a host/embedded language pairing. Actually, Mun is completely written in Rust, building on similar crates as rust-analyzer and rustc. Its key features include:
-
rust-analyzer changelog #159
#13728 upgrade chalk to make solver fuel work again (works around most trait solving hangs).
-
rust-analyzer changelog #147
#13221 (first contribution) add option to move lenses above doc comments (rust-analyzer.lens.location):
-
Does Rust need proc-macros 2.0?
Rust-analyzer has a good overview: https://github.com/rust-analyzer/rust-analyzer/blob/master/docs/dev/syntax.md
-
rust-analyzer changelog #134
#12517 (first contribution) fix completion for methods in trait generated by macro.
-
LSP Rust Analyzer keeps telling me `Error NO_RESULT_CALLBACK_FOUND`
-- all the opts to send to nvim-lspconfig -- these override the defaults set by rust-tools.nvim -- see https://github.com/neovim/nvim-lspconfig/blob/master/doc/server_configurations.md#rust_analyzer server = { -- on_attach is a callback called when the language server attachs to the buffer -- on_attach = on_attach, settings = { -- to enable rust-analyzer settings visit: -- https://github.com/rust-analyzer/rust-analyzer/blob/master/docs/user/generated_config.adoc ["rust-analyzer"] = { -- enable clippy on save checkOnSave = { command = "clippy" }, assist = { importGranularity = "module", importPrefix = "self", }, cargo = { loadOutDirsFromCheck = true }, procMacro = { enable = true }, } } },
-
rust-analyzer changelog #130
#12349 publish universal VSIX to make Code happy.
vim-lsp-settings
-
LSP with pylsp: it work-ish but autocompletion and hover randomly work.
I am reading here but still... it seems all OK. It is weird that it was working with ALE with the current setup. Anyway, I noticed that every once in a while I get this error when I change buffer.
-
small vimrc and lsp?
There's https://github.com/mattn/vim-lsp-settings to save even more lines, which is I think what OP wants.
-
Recommended minimal set of plugins for a great experience
vim-lsp-settings makes installing lsp for vim-lsp trivial: :LspInstallServer
- Starting with linux, my experience
- Does vim have a built in/plugin version of vscode's command click?
-
How to turn off vim-lsp-settings and background highlight for similar occurrences
Hello everyone, I have this problem when using vim-lsp-settings, that every time my cursor passes through a word (sorry I don't have enough information to derive what type of word, but take Type, Function in Python, or constants (like g:lsp_diagnostics_signs_enabled) and has() in vimrc) it always showing similar occurrences of the word, and I don't want that. Not only it takes some time (highlighting that word cursor is on, and when moving cursor really fast it couldn't catch up), it's usually something I don't really need (well, if it could be configured to be faster and my laptop won't screeching then I'm all in - I'm using thinkPad x270).
-
is anyone using preservim/tagbar with typescript?
I use vim-lsp plugin which only needs a few lines of config. It has several JavaScript language servers listed in vim-lsp-settings.
- Plugins to have VS code tools
-
From vscode to vim
Then lsp. All four of these: prabirshrestha/vim-lsp; mattn/vim-lsp-settings; prabirshrestha/asyncomplete.vim; prabirshrestha/asyncomplete-lsp.vim
-
Project & File navigation
vim-lsp that can be bootstrapped with vim-lsp-settings, for jumping to definitions, etc.
What are some alternatives?
vscode-rust - Rust extension for Visual Studio Code
nvim-lspconfig - Quickstart configs for Nvim LSP
Clippy - A bunch of lints to catch common mistakes and improve your Rust code. Book: https://doc.rust-lang.org/clippy/
php-language-server - PHP Implementation of the VS Code Language Server Protocol 🆚↔🖥
intellij-rust - Rust plugin for the IntelliJ Platform
flutter-tools.nvim - Tools to help create flutter apps in neovim using the native lsp
rustfmt - Format Rust code
NvChad - Blazing fast Neovim config providing solid defaults and a beautiful UI, enhancing your neovim experience.
eglot - A client for Language Server Protocol servers
rust-analyzer - A Rust compiler front-end for IDEs
rust - Empowering everyone to build reliable and efficient software.
LazyVim - Neovim config for the lazy