Notes

evergreen

The Patch Bram Applied

A small contribution to Vim, the man who took it, and the editor I still open every morning.

· · 5 min read

vim, open-source, tribute

Vim is Charityware. You can use and copy it as much as you like, but you are encouraged to make a donation for needy children in Uganda.

— Vim's :help uganda (runtime/doc/uganda.txt)

Cite this
APA
Mangalapilly, Y. J. (2026, April). The Patch Bram Applied. Saṃhitā Notes. https://yesudeep.com/blog/the-patch-bram-applied/
BibTeX
@online{mangalapilly2026the,
          author  = {Yesudeep Jose Mangalapilly},
          title   = {The Patch Bram Applied},
          journal = {Sa\d{m}hit\=a Notes},
          year    = {2026},
          month   = {April},
          url     = {https://yesudeep.com/blog/the-patch-bram-applied/},
          urldate = {2026-07-01},
        }
Plain
Yesudeep Jose Mangalapilly. “The Patch Bram Applied.” Saṃhitā Notes, 2026. https://yesudeep.com/blog/the-patch-bram-applied/.
RIS
TY  - ELEC
        AU  - Mangalapilly, Yesudeep Jose
        TI  - The Patch Bram Applied
        T2  - Saṃhitā Notes
        PY  - 2026
        UR  - https://yesudeep.com/blog/the-patch-bram-applied/
        Y2  - 2026-07-01
        ER  - 

A short, personal one — not a systems dissection. It's about a tiny patch I sent to Vim, the fact that Bram Moolenaar applied it himself, and what it has meant to keep using his editor after he was gone.

I open Vim almost every morning. I have used Emacs and Vim for most of my career — across editor flirtations and operating-system changes and jobs, the muscle memory persists; hjkl is closer to instinct than to thought. For most of those years the editor was, in a quiet way, maintained. Even my Emacs configuration is powered by Spacemacs, which is built on top of evil-mode, so I use the same bindings in both editors.

None of that fluency was innate; it was installed. Early in my career my mentor turned off the GUI on my Linux machine and told me to do everything — editor included — in the terminal. Thrown into the deep end like that, I learned Vim the only way that really sticks: with no comfortable thing to retreat to. The exercise switched on parts of my brain I didn't know I had, and within weeks the modal grammar stopped being something I fought and became something I think with.

That private fluency is the flip side of a very public joke: the internet long ago decided Vim's most notorious feature is that you can't get out of it"How do I exit the Vim editor?" has drawn millions of views on Stack Overflow. The flailing is a genre:

:q
:quit
:exit
quit
ZZ
^C  ^C
:help i'm stuck

The secret, for the record, is :q (:q! if you've made a mess). Muscle memory spares you the panic now — but everyone has stared at that screen once.

In September 2020 I sent a small patch to Vim. It was nothing clever — Vim already knew that files named BUILD, BUILD.bazel, and *.bzl were Bazel files, but it didn't recognize the *.BUILD extension that external-repository rules use. So syntax highlighting silently went missing on a class of files I edited every day. I filed an issue, then a patch to fix it: teach the filetype detector two more extensions, *.BUILD and *.bazel. Ten lines, counting the patch-number bump.

Bram reviews

The patch landed as Vim patch 8.2.1566, and the commit's author and committer are the same name: Bram Moolenaar. Not a bot, not a triage team, not a delegated maintainer. The man who wrote Vim read my ten-line patch, decided it was right, and applied it.

If you've only ever contributed to projects with CI gatekeepers and review rotations, it's hard to convey how that felt. Vim was, for its whole life, a benevolent dictatorship in the old, literal sense: Bram personally read the contributions, decided what was good for the program, and merged them himself. My change is, by any measure, insignificant. But it is in there — and because it's in there, it was later ported into Neovim too, where it still sits in the core filetype table. A footgun I hit once is now quietly handled for everyone who edits a *.BUILD file in either editor.

The strange, generous arithmetic of open source: a small thing you did for yourself becomes a small thing done for everyone, forever.

Bram Moolenaar

Bram Moolenaar (1961–2023) completed the first public version of Vim in November 1991 — the name then stood for "Vi IMitation," and only grew into "Vi IMproved" around version 2.0 (1993), once there were enough improvements to justify it. He maintained it, largely himself, for the rest of his life, spending fifteen years at Google's Zürich office, working on Calendar, and kept maintaining Vim the whole time.

The detail that says the most about him isn't technical. In 1995 he made Vim charityware. The software is free; the license asks only that, if you find it useful, you consider donating to help children in Uganda — through ICCF Holland, the foundation he started to support children orphaned by AIDS at the Kibaale Children's Centre. Type :help uganda in any Vim, today, and you'll find the appeal still there, shipped inside the editor, where it has been for thirty years. (The foundation itself has since passed the torch: after Bram's death, ICCF Holland transferred its work to its sister charity Kuwasha in Canada and dissolved at the end of 2025 — :help uganda now points there, and donations still go directly to Uganda.) He built one of the most-used pieces of software in the world and pointed the gratitude it earned at children he would never meet.

Bram died on August 3, 2023, at 62, of a rapidly developing illness. Vim goes on — Christian Brabandt and the community maintain it now, with the care it deserves. But something is different about opening it since. The program is exactly the same; the hand behind it is gone.

The best software outlives the people who made it — and that is both the consolation and the loss.

I think about that little patch sometimes, when I open a *.BUILD file and the colors come up right. It's the smallest possible monument: a few lines of a filetype table, in two editors, that work because a man in Zürich read what a stranger sent him and decided it was good. I never met him. I use his gift every day. :help uganda.

Thank you. Rest in peace, Bram.

Lessons

  • Open source allows individual developers to solve local friction and share the solution globally.
  • Vim was historically maintained as a benevolent dictatorship by Bram Moolenaar, who reviewed and applied patches directly.
  • Small additions propagate across the ecosystem (e.g., from Vim to Neovim), silently helping others for years.
  • The charityware model (:help uganda) shows how gratitude for high-quality software can support real-world humanitarian causes.

References

  1. Vim.” — · the patch and the commit Bram applied
  2. ICCF Holland.” — Bram's foundation, dissolved end of 2025 · Kuwasha, the sister charity :help uganda points to now
  3. Bram Moolenaar.” — · the announcement of his passing (August 2023)
  4. Neovim.” — where the change also lives

How to cite

APA
Mangalapilly, Y. J. (2026, April). The Patch Bram Applied. Saṃhitā Notes. https://yesudeep.com/blog/the-patch-bram-applied/
BibTeX
@online{mangalapilly2026the,
          author  = {Yesudeep Jose Mangalapilly},
          title   = {The Patch Bram Applied},
          journal = {Sa\d{m}hit\=a Notes},
          year    = {2026},
          month   = {April},
          url     = {https://yesudeep.com/blog/the-patch-bram-applied/},
          urldate = {2026-07-01},
        }
Plain
Yesudeep Jose Mangalapilly. “The Patch Bram Applied.” Saṃhitā Notes, 2026. https://yesudeep.com/blog/the-patch-bram-applied/.
RIS
TY  - ELEC
        AU  - Mangalapilly, Yesudeep Jose
        TI  - The Patch Bram Applied
        T2  - Saṃhitā Notes
        PY  - 2026
        UR  - https://yesudeep.com/blog/the-patch-bram-applied/
        Y2  - 2026-07-01
        ER  - 

Annotations

Thank you — your note is held for review and will appear once approved.

Thank you — your note is published.

Please sign in below to leave a note.

Type to search · ↑↓ to move · ↵ to open · Esc to close