 |
VOOZH | about |
:put =toupper(@")
Registers in Vim are not only for raw replay; you can treat them as string data and transform them at paste time.
category: registers tags: #registers #expression-register #editing #vimscript
:let @q = substitute(@q, '\n', '', 'g')
A common macro failure mode is accidentally hitting while recording.
category: macros tags: #macros #registers #debugging #vimscript
:let @a = @a[:-2]
Macros and named registers are just strings, so you can surgically edit them instead of re-recording from scratch.
category: registers tags: #registers #macros #vimscript #editing
:let @q = substitute(@q, '\n$', 'A;<Esc>\n', '')
Rerecording a long macro for one tiny change is slow and error-prone.
category: macros tags: #macros #registers #automation #vimscript
:echo getreg('a', 1, 1)
For advanced register debugging and macro tooling, plain getreg('a') is often not enough.
category: registers tags: #registers #vimscript #debugging #automation
:call setreg('b', getreg('a'), getregtype('a'))
Plain register copies like :let @b = @a move text, but they can lose important metadata about register type.
category: registers tags: #registers #advanced #vimscript #editing
:call setreg('a', "foo\nbar", 'b')
Most register examples focus on interactive yanks, but setreg() lets you construct registers programmatically, including their type.
category: registers tags: #registers #vimscript #automation #editing
:s/\v\d+/\=printf('%04d', submatch(0))/g
Substitution expressions let Vim compute each replacement dynamically, which is ideal when plain capture groups are too limited.
category: editing tags: #editing #substitution #regex #vimscript
:let @a .= getline('.') . "\n"
Named registers are usually filled with yanks and deletes, but they are also plain variables you can edit with Vimscript.
category: registers tags: #registers #command-line #vimscript #editing
luaeval('lua_expression')
When you have existing Vimscript code that needs to reach into Neovim's Lua ecosystem, luaeval() is the bridge.
category: config tags: #neovim #config #vimscript #lua
json_encode()
Vim 8.
category: config tags: #config #vimscript #ex-commands
glob()
The glob() built-in function expands a wildcard pattern into a list of matching filesystem paths, entirely within Vimscript.
category: config tags: #config #vimscript #files #ex-commands
<SID>
(Script ID) is a Vimscript token that expands to a unique, per-script prefix at runtime.
category: config tags: #config #vimscript #mappings #functions #normal-mode
:lua {code}
Neovim's :lua command lets you run arbitrary Lua code inline from the command line.
category: command-line tags: #command-line #lua #neovim #vimscript #advanced
setreg()
The setreg(reg, value, type) and getreg(reg, 1, 1) functions give you full programmatic control over registers, including their type (characterwise, linewise, o
category: registers tags: #registers #vimscript #macros #ex-commands
vim.api.nvim_buf_call()
vim.
category: config tags: #ex-commands #vimscript #buffers #config
vim.on_key()
vim.
category: config tags: #ex-commands #vimscript #config #macros
vim.schedule()
vim.
category: config tags: #ex-commands #vimscript #config #completion
:debug
The :debug command prefix puts Vim into its built-in interactive debugger before executing the given command.
category: command-line tags: #ex-commands #debugging #command-line #vimscript
has('feature')
The has('feature') function returns 1 if the specified feature is available in the current Vim/Neovim instance, 0 otherwise.
category: config tags: #config #vimscript #portability