vim-classic mit Homebrew, apk installieren

Projektlinks

• Homepage
• Repository
• Upstream-Dokumentation
• Paketmanager-Seite

Befehle und Aliase

In der lokalen Paketdatenbank wurden keine Executable-Aliase gefunden.

Projektgeschichte

Drew DeVault announced the fork in March 2026 after deciding he did not want to use Vim and Neovim codebases that accepted LLM-assisted development. He chose Vim 8.2.0148 as the base because it was the patch immediately before Vim9 Script entered upstream Vim, making Vim Classic intentionally compatible with older Vim plugins and workflows while avoiding the newer Vim9 language line.

The first public release, Vim Classic 8.3.0, was announced on June 2, 2026. The release was based on Vim 8.2.0148 with selected upstream bug fixes and security patches conservatively backported, and the announcement explicitly warned that the fork had not reviewed every upstream patch since that base.

Adoptionsgeschichte

Vim Classic is an early-stage fork rather than a broad replacement for upstream Vim. Its adoption story is mostly ideological and compatibility-driven: it targets users who want Vim 8 behavior, legacy plugin compatibility, and a maintenance policy that rejects generative AI assistance.

Wie es verwendet wird

In daily use, Vim Classic is meant to be used like Vim: the editor keeps Vim's modal editing model, command-line commands, help system, vimrc conventions, and vi/Vim muscle memory. The project documentation points users to the normal Vim help model, including reading help inside the editor.

Warum Paket-Nerds sich dafür interessieren

For package maintainers and terminal-editor users, Vim Classic is notable less as a new editor interface and more as a policy fork: it freezes around a Vim 8-era compatibility point, backports selected fixes, and creates a packageable alternative for users who object to LLM-assisted upstream development.

Zeitleiste

• 2026-03-25: Drew DeVault publicly describes forking Vim and choosing Vim 8.2.0148 as the base.
• 2026-06-02: Vim Classic 8.3.0 is released as the first stable long-term-support fork release.

Related projects

• Vim Classic is directly derived from Vim, deliberately stopping before Vim9 Script. It is also discussed in contrast with Neovim, another major Vim-family fork, and with upstream Vim's continuing post-Bram maintenance.

Quellen

• https://drewdevault.com/blog/Forking-vim/
• https://vim-classic.org/
• https://vim-classic.org/doc/intro.html
• https://vim-classic.org/news/vim-8.3-released.html