Neovim-from-scratch
rust-analyzer
Neovim-from-scratch | rust-analyzer | |
---|---|---|
81 | 207 | |
5,252 | 9,320 | |
0.6% | - | |
5.0 | 10.0 | |
about 2 months ago | about 2 years ago | |
Lua | Rust | |
GNU General Public License v3.0 only | 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.
Neovim-from-scratch
-
How to configure vim like an IDE
They also provide a "from-scratch" option, to be easier to understand
-
New User C Setup Help?
I would recommend the Neovim from Scratch series on Youtube with the addition of the code_runner.nvim plugin. It's a good config that will teach you a lot about configuring Neovim. code_runner.nvim is a nice addition, especially for a university student. Good luck!
-
How to learn neovim
I don't know myself how I learned neovim, but I started with using a repo called Neovim-from-scratch, but I'm not sure if it's still up to date, but I used it as my base config then started to add plugins I want and remove plugins I don't need. Most of the people recommend kickstart.nvim now as base config for neovim lua config.
- [nvChad] lspconfig
-
NOOB Needs help
Hey So I am trying to setup the neovim config for gopls and ts-server using [this](https://github.com/LunarVim/Neovim-from-scratch/tree/06-LSP), Now I would like to clarify that I have copy pasted from this guys repo and I do understand what he is doing to some extent. But for some reason in the file `lua/user/lsp/handlers.lua` He creted the following function ```lua local function lsp_keymaps(bufnr)
- [Neovim] Question de débutant sur le chargement de NVIM-Web-Devicons
- Is there a good neovim plugin that integrates a pre-configured lsp+treesitter+telescope?
-
Help with getting started with Neovim
This is the GitHub repo for the aforementioned playlist.
-
Opinions on pre-made configurations (e.g. LunarVim, AstroNvim)
I would recommend LazyVim or Kickstart.nvim. If you don't want to do any configuration, LunarVim might be for you. I would recommend the Neovim from Scratch config since it is very good and essentially has an accompanying guide. However, it is slightly out of date and needs a few tweaks to work properly.
- Migrating from VSCode to Neovim
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.
What are some alternatives?
LunarVim - 🌙 LunarVim is an IDE layer for Neovim. Completely free and community driven.
vscode-rust - Rust extension for Visual Studio Code
kickstart.nvim - A launch point for your personal nvim configuration
Clippy - A bunch of lints to catch common mistakes and improve your Rust code. Book: https://doc.rust-lang.org/clippy/
AstroNvim - AstroNvim is an aesthetic and feature-rich neovim config that is extensible and easy to use with a great set of plugins
intellij-rust - Rust plugin for the IntelliJ Platform
vim-surround - surround.vim: Delete/change/add parentheses/quotes/XML-tags/much more with ease
rustfmt - Format Rust code
LazyVim - Neovim config for the lazy
eglot - A client for Language Server Protocol servers
zls - A Zig language server supporting Zig developers with features like autocomplete and goto definition
rust - Empowering everyone to build reliable and efficient software.