Enable Neovim's Built‑in LSP for Python with pyright
Learn how to activate Neovim’s built‑in LSP client for Python using pyright, with step‑by‑step installation, configuration, verification, and troubleshooting.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how to activate Neovim’s built‑in LSP client for Python using pyright, with step‑by‑step installation, configuration, verification, and troubleshooting.
Learn how to use Neovim’s Lua‑based LSP client and async job control to create responsive, floating diagnostics and run external formatters without blocking the editor. The article covers a concrete example, trade‑offs, and best‑practice checks.
Learn how Neovim's Lua API isolates plugin code from the core editor, what trust boundaries exist, and how to verify safe operation.
The .norg format is Neorg's purpose-built plain-text markup for Neovim notes and tasks. Here's what the syntax looks like, what it does well, and where the ecosystem trade-offs bite.
Explore how Neorg uses document-level metadata blocks to store structured project data and file attributes without cluttering the main content.
Neovim's move to Lua isn't just syntax preference — it's compiled execution, a module-based API, and config-as-code. Here's what you gain, what to leave alone, and how to measure the difference.
Neovim’s native Lua runtime cuts startup time by 30‑70 %. This post explains the performance gap, shows how to migrate a Vimscript plugin to Lua, and lists practical trade‑offs.
Neorg's built-in query engine (norg.query) searches thousands of .norg files using structured metadata, TODO states, and heading hierarchy — all inside Neovim via the same treesitter parser. Covers metadata format, Lua API, a weekly review example, and scale limits.
Learn how to enable Neovim’s native Language Server Protocol client, configure a server like clangd, verify it works, and understand the trade‑offs involved.