Modeless Vim

Original Article ↗ Hacker News Discussion ↗

A Vim configuration that removes modal editing in favor of familiar GUI-style shortcuts (Ctrl‑S to save, Shift+arrows to select, Ctrl‑C/V to copy/paste) is dividing terminal users. Supporters like that it lets people who mainly use editors such as VS Code still benefit from Vim’s ubiquity, syntax highlighting, and plugins when they occasionally drop into a remote shell. Critics counter that it undermines Vim’s core strength—modal, composable commands—and suggest alternatives like Vim’s built‑in “easy mode,” Emacs with CUA/Evil modes, or other modeless terminal editors such as micro instead.

Purpose & Intended Use Cases

  • Config turns Vim into a modeless, GUI-like editor (Ctrl‑S save, Shift+arrows selection, Ctrl‑C/V, etc.).
  • Targeted at people who normally use GUI editors (e.g., VSCode) but occasionally need a terminal editor, especially over SSH.
  • Some users report wanting Vim’s syntax highlighting and ecosystem when their preferred modeless terminal editor (e.g., micro, nano) falls short or isn’t available.

Comparison to Existing Options

  • Multiple commenters note Vim’s built‑in “easy mode” (vim -y / evim) and mswin.vim already move Vim toward CUA/Windows behavior.
  • Others point to alternative terminal editors (micro, nano, mcedit) or just using a remote-capable GUI (VSCode remote, Sublime + remote plugins, Emacs -nw).
  • Question raised: if you’re allowed to install this config on a remote box, why not install your preferred editor instead? Counter: on shared/locked‑down systems you can often tweak $HOME but not install packages.

Modal vs Modeless Debate

  • Many defend Vim’s modes as its core strength: composable motions, efficiency, low mouse usage, reduced finger contortions, helpful for RSI.
  • Others argue modes are confusing, increase user errors, and conflict with ubiquitous CUA shortcuts learned across apps.
  • Some say “all editors are modal” in a loose sense (focus changes behavior); others insist Vim’s modes are qualitatively different because the same text area changes meaning of every key.

Learning Curve, Memorization & Discoverability

  • Several admit they repeatedly “half‑learn” Vim, then forget commands because they use it rarely.
  • Opposing view: basic motions can be learned in minutes; with practice, Vim feels natural and fast.
  • Suggestions for gentler learning: cheat‑sheet backgrounds, which‑key style popups, or using modal editors like Helix/Kakoune that surface possible motions interactively.

Ergonomics & Keybinding Culture

  • Large subthread on remapping Caps Lock to Escape (often tap=Esc, hold=Ctrl) as essential for comfortable Vim use; others prefer Caps→Ctrl or continue using Ctrl‑[ / jk mappings.
  • Debate over reclaiming legacy TTY shortcuts like Ctrl‑S / Ctrl‑Q, and how terminals and TUIs should handle them in 2024.

Portability, Philosophy & Reactions

  • Some argue over‑customizing tools reduces ability to use default setups on random machines; others maintain version‑controlled dotfiles or portable binaries to carry configs everywhere.
  • Reactions range from “useful hack for my exact use case” to “heresy” and “pointless—just learn 10 Vim keys or use nano/micro.”
  • General meta‑point: editor choice is personal; several urge dropping the culture-war tone around Vim vs Emacs vs GUI IDEs.