ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #neovim
A task guide to make Norg checklist items parse and toggle in nvim-orgmode by verifying filetype Treesitter parser activation and the checklist toggle action, with checks and recovery steps.
Configure hover, definitions, and diagnostics with vim.lsp and vim.diagnostic before deciding whether you need an LSP plugin.
Switch from a Vimscript <code>vimrc</code> to a Lua <code>init.lua</code> in Neovim. This guide walks through the steps, shows example conversions, validates settings, and covers recovery options for a smooth transition.
Neovim's vim.lsp handles JSON‑RPC and diagnostics but ships no server configs. Minimal design: core vim.lsp plus nvim‑lspconfig recipes, completion only if needed. Servers run as your user, so pin versions and gate per‑project enablement.
Keep Vim undo history after quitting: enable undofile, manage the undo directory, and understand the privacy and size trade-offs.
Neovim’s core LSP client replaces external plugins, offering a minimal, stable foundation for language features. Learn how to configure it, see a concrete Python example, and understand the trade‑offs with richer plugins.
Architecture note on using Neovim's built-in LSP client as the language-intelligence layer: minimal native Lua config, trust boundaries, health checks, failure modes, and when to adapt for remote development.
Configure multiple Neorg workspaces in core.dirman, switch between them, and verify where journals and links resolve.
An architectural analysis of Neovim's shift from Vimscript to LuaJIT, focusing on the C-API bridge, memory boundaries, and performance verification.
norg
lua