Skip to main content
Vorto follows Vim’s modal grammar, so most of your muscle memory transfers directly. This page is the honest map: what works the same, what Vorto gives you for free that Vim needs a plugin for, and what isn’t there yet. For the full keymap, see Default keybindings.

​
What works the same

If you think in Vim’s operator + motion grammar, it works here:

​
What Vorto adds out of the box

Things that need a plugin (or aren’t possible) in stock Vim ship in the binary:
  • Surround — ys{motion}{char}, cs{old}{new}, ds{char}, with a which-key hint. No vim-surround to install. See Keybindings.
  • Comment toggles — gc{motion} for line comments and gb{motion} for block comments, count- and multi-cursor-aware.
  • Multiple cursors — + adds a cursor at the next match of the word under the cursor, - removes the last one.
  • LSP, tree-sitter, fuzzy finding, file explorer, and Copilot — all built in rather than assembled from plugins. See Why Vorto.
  • Tree-sitter text objects — if / af (function), ic / ac (class), ia / aa (argument) work once the grammar is installed.

​
Not in Vorto today

These Vim features are not implemented yet. If your workflow leans on them, that’s worth knowing before you switch:

​
Intentionally different

Some Vim conventions are left out on purpose, not pending:
  • Config is TOML, not Vimscript. Keybindings, options, and per-language settings live in one ~/.config/vorto/config.toml file. There is no init.vim, no :set runtime command, and no autocmd system. See Configuration overview.
  • A focused set of : commands. Vorto implements the everyday ex commands — file, buffer, window, search, and substitution — rather than the full ex language. See the command reference.
  • Ctrl-r redo may need binding. Redo is available as the redo action; bind it in config if it isn’t already mapped.
Ready to dig in? The Default keybindings page lists every bound key, and Editing modes covers the modal model in depth.