ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
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.
Choosing between Lua and Vimscript autocommands for filetype detection The goal is to register filetype-specific triggers using either nvim_create_autocmd in Lua or the legacy autocmd command in Vimscript. Lua provides type-safe arguments and direct API integration, while Vimscript is evaluated at runtime by the Vim engine. The main constraint is version sup
I run vim non-interactively on a low-traffic server to apply scripted edits over many files, and I want to cut unnecessary terminal redraw overhead. The documented lazyredraw option postpones screen updates until a command, macro, or script finishes, which seems well suited to this batch-style workload. What I am unsure about is the boundary of the setting.
Configuration Load Sequence Neovim allows the coexistence of legacy Vimscript and modern Lua configurations, typically transitioning from init.vim to init.lua . While vim.fn enables Lua to call Vimscript functions, the execution order between these two languages can become ambiguous when complex plugin dependencies are involved. Component: LuaJIT Interpreter
lua
neovim
vim