Neovim LSP Setup Guide: Autocomplete, Diagnostics, and Code Intelligence in Terminal

LSP Brings the IDE to Terminal

Neovim LSP setup tutorial with mason.nvim and nvim-cmp. Configure autocomplete, diagnostics, go-to-definition, code actions, and format-on-save for a full IDE in terminal.

Neovim's Lua API means your editor config is a real program — not a pile of Vimscript variables. You get functions, loops, conditionals, and lazy loading for free.

By the end of this 20 min guide, you'll have a working Neovim setup and practical Neovim workflows you can use immediately.

• Understand what Neovim does and why it matters for Development
• Install and configure Neovim for your environment
• Build Neovim-specific workflows with real examples
• Troubleshoot common Neovim issues with concrete fixes

Installing Language Servers

Install Neovim:

brew install neovim ripgrep

• Development environment with appropriate permissions
• Prior experience with Neovim
• A terminal with true color support
• Git for version-controlling your config

nvim-lspconfig Basics

Structure your config into modular files under lua/. Each file handles one concern: options, keymaps, plugins, autocmds.

Here's a foundational configuration to start with:

-- keymaps.lua
vim.keymap.set("n", "w", ":w", { desc = "Save" })
vim.keymap.set("n", "q", ":q", { desc = "Quit" })
vim.keymap.set("n", "e", ":NvimTreeToggle", { desc = "Toggle file tree" })

• Begin with this config and make small, incremental changes
• Document each setting with inline comments
• Test changes one at a time to isolate issues
• Keep your config in a Git repo for easy rollback and sharing

Autocomplete with nvim-cmp

With Neovim configured, these Neovim-specific workflows will save you time every day:

• <leader>ff find files with Telescope
• <leader>fg live grep across project
• gd go to definition via LSP
• gr list references
• <C-h/j/k/l> navigate window splits

Diagnostics, Formatting & Hover

Once you're comfortable with Neovim basics, these advanced techniques will transform your Neovim workflow:

• Lazy-load plugins on specific events or keys for instant startup
• Use autocmd to run code on file type changes
• Integrate LSP for go-to-definition and hover docs
• Add Treesitter for AST-based syntax highlighting

LSP Not Attaching? Debugging

Here are the most common Neovim issues and how to fix them:

• LSP not attaching? Run :LspInfo to check active clients
• Treesitter errors? Run :TSUpdate to update parsers
• Plugin missing? Run :Lazy sync to install all
• Slow startup? Run :Lazy profile to find the bottleneck

IDE-Quality Editing

Congratulations — you now have a solid Neovim foundation. Here's where to go next:

• Explore the official Neovim documentation for features not covered here
• Join the Neovim community (GitHub Discussions, Discord, or Reddit)
• Check the related tutorials below for deeper Neovim dives
• Build your own Neovim configuration and share it with the community