Skip to content

mini.nvim

Status: 🌿

Problem

Need a cohesive Neovim toolkit with low configuration overhead and a single ecosystem for common editor capabilities.

Why This Choice

  • mini.nvim is the base of the setup and also provides the dependency flow via mini.deps.
  • It reduces plugin sprawl by covering many concerns with consistent APIs and behavior.

Current Usage

  • Dependency manager: mini.deps (add, update, clean).
  • File/navigation: mini.files, mini.pick, mini.visits.
  • Git and diffs: mini.git, mini.diff.
  • Editing ergonomics: mini.ai, mini.comment, mini.move, mini.operators, mini.splitjoin, mini.surround, mini.trailspace.
  • UI and buffers: mini.statusline, mini.tabline, mini.notify, mini.bufremove, mini.colors, mini.jump, mini.extra, mini.basics.

Keybindings in Use

  • Space p u: update plugins (mini.deps.update).
  • Space p x: clean plugins (mini.deps.clean).
  • Space e: open file explorer (MiniFiles.open).
  • Space o: focus file explorer on current buffer path.

Caveats

  • Broad module usage means updates can affect multiple workflows at once.
  • It helps to keep quick smoke tests after plugin updates.

Removal Criteria

  • If module overlap grows with external plugins or upgrade risk becomes too high, split responsibilities into narrower plugins.