Vim Workflows and Config Tips for Linux Sysadmins

Vim remains one of the most efficient editors available on Linux and Unix systems. While it has a steep learning curve, the payoff in speed and capability is substantial once you develop muscle memory. This guide covers practical configuration strategies, essential keybindings, and workflow improvements that actually matter in daily use.

Setting up your configuration

A solid .vimrc (or init.vim/init.lua for Neovim) provides the foundation for an effective setup. Rather than starting from scratch, consider using a well-maintained configuration as a base and customizing from there.

For version control, store your dotfiles in a Git repository:

cd ~
git clone https://github.com/yourusername/dotfiles.git ~/.config/nvim
# For traditional Vim:
ln -s ~/.config/nvim/init.vim ~/.vimrc

If migrating from an existing setup, carefully merge settings rather than overwriting. Key areas to configure:

• Plugin manager: Use lazy.nvim for Neovim (faster startup) or vim-plug for traditional Vim
• Leader key: Set to a key you can reach easily (many use space: let mapleader = " ")
• Color scheme: Choose one that works for your terminal (try tokyonight, gruvbox, or nord)
• Tab and indent behavior: Consistent shiftwidth, tabstop, and expandtab settings
• Language-specific settings: File type detection and formatting rules

Version control your dotfiles so you can sync across machines and revert problematic changes quickly.

Movement and navigation

Home row navigation keeps you efficient:

• h, j, k, l for movement (disable arrow keys in your config to build the habit)
• w (next word), b (previous word), e (end of word), ge (end of previous word)
• f<char> to jump to a character on the current line; ; repeats forward, , repeats backward
• /<pattern> to search forward, ?<pattern> to search backward
• * to search for the word under the cursor
• G to go to end of file, gg to go to start, :<number> or <number>G to jump to a specific line
• % to jump between matching brackets, parentheses, or braces

Use counts with motions: 3w moves three words forward, 5j moves five lines down. This is faster than repeated keypresses.

Text selection and editing

Vim’s selection modes give you precise control:

• Visual character mode (v): Select individual characters
• Visual line mode (V): Select entire lines (useful for moving blocks of code)
• Visual block mode (Ctrl+V): Select columns; perfect for multi-line edits or adding comments to multiple lines

Combine selection with operations:

• d<motion> deletes (e.g., dw deletes a word, d$ deletes to end of line)
• c<motion> deletes and enters insert mode (e.g., cw changes a word)
• y<motion> yanks (copies) text
• gq formats (wraps) selected text to textwidth

For complex edits, use visual block mode with I (insert at start) or A (append at end):

" To comment multiple lines in a config file:
1. Ctrl+V to enter block mode
2. Move down to select all lines
3. I to insert at the start
4. Type # and space
5. Esc to apply to all selected lines

Search and replace

Replace operations are powerful but need care:

• :s/old/new/ replaces the first occurrence on the current line
• :s/old/new/g replaces all occurrences on the current line
• :%s/old/new/g replaces globally in the entire file
• :%s/old/new/gc replaces globally with confirmation on each match (safer for large changes)
• :5,20s/old/new/g replaces only in lines 5–20

Use regex patterns for complex replacements. For example, :%s/\(.*\)_old/\1_new/ swaps suffixes while preserving prefixes.

Working with multiple files and splits

Vim’s buffer and split system allows efficient multi-file editing:

Buffers (in-memory file list):

• :bn (next buffer), :bp (previous buffer)
• :b <name> jump to a specific buffer
• :ls list all open buffers
• :bd close a buffer without closing Vim

Splits (visible windows):

• Ctrl+W followed by s (horizontal split), v (vertical split)
• Ctrl+W followed by arrow keys or h/j/k/l to switch between splits
• Ctrl+W followed by = to equalize split sizes, | to maximize width, _ to maximize height

For working with a project directory structure, use Netrw (built-in):

" Open file browser
:e .
" Or configure a key:
nnoremap <leader>f :Explore<CR>

Alternatively, use vim-vinegar or nvim-tree for a better file browsing experience.

Neovim-specific features

Neovim 0.9+ includes native LSP support—no complex setup required. Install the nvim-lspconfig plugin and enable LSP for your languages:

-- init.lua
require('lspconfig').pyright.setup({})   -- Python
require('lspconfig').ts_ls.setup({})     -- TypeScript
require('lspconfig').rust_analyzer.setup({}) -- Rust

Pair LSP with a completion framework like nvim-cmp:

local cmp = require('cmp')
cmp.setup({
  sources = cmp.config.sources({
    { name = 'nvim_lsp' },
    { name = 'buffer' },
  })
})

Neovim also supports Lua configuration (faster and more expressive than pure VimScript):

-- init.lua
vim.opt.number = true
vim.opt.expandtab = true
vim.opt.shiftwidth = 4
vim.opt.textwidth = 80
vim.keymap.set('n', '<leader>w', ':w<CR>', { noremap = true })

Practical habits to build efficiency

• Learn one command per session: Master movement first, then selection, then operations. Rushing to memorize everything leads to muscle memory failures.
• Use counts liberally: 10j is faster than holding down j.
• Map frequently-used operations: Create custom keybindings for commands you use daily.
• Practice visual mode: It’s intuitive and faster for many edits than remembering complex motions.
• Use marks for large jumps: m<letter> sets a mark, '<letter> jumps to it. Useful for navigating large files.

Resources for deeper learning

• :help within Vim accesses comprehensive documentation
• vimtutor is a built-in interactive tutorial (run it from the terminal)
• Browse community configurations at github.com/dotfiles/dotfiles for configuration inspiration
• vim.fandom.com covers advanced techniques and edge cases
• Practice with real work rather than drills—muscle memory develops faster with actual editing tasks