Vim's UserGettingBored Joke Autocmd Never Triggers
Tracing the history of Vim's joke UserGettingBored entry and the 2022 extension that brought it to life.
Vim’s autocmd list still contains a joke entry that never executes. Its name is UserGettingBored. The documentation describes it as occurring when the user presses the same key 42 times. It ends with a smiley, making clear it is a joke.
According to reporting by evanhahn.com via raymii on Lobsters, this entry exists only in documentation and test code. Attempting to register it as an autocmd returns a no such group or event error. Despite having no behavior, it is notable that the description remains in Vim, Neovim, and Vim Classic alike.
Autocmds are a mechanism for executing commands or functions triggered by specific events. More than 100 events are defined, ranging from buffer creation to file saving. Users can bind a write command to the TextChanged event to achieve autosave-like behavior. It is a core feature for extensibility.
One Joke Hidden Among Over 100 Events
Autocmd events are tied to milestones in editing work. Fine-grained triggers are provided, including entering and leaving buffers, reading and writing, and focus movement. Users can assign handling to suit their needs and reduce repetitive work. The documentation strictly defines the conditions under which each event fires.
Among them, the UserGettingBored description stands out. The original documentation reads as follows.
UserGettingBored: When the user presses the same key 42 times. Just kidding! :-)
The condition of pressing the same key 42 times lacks the specificity of other event definitions. The number 42 is widely known as a cultural reference originating in a British science-fiction novel. The trailing smiley shows it is play, not specification. It reads as blank space left in serious reference documentation.
This entry has no execution infrastructure. If registration is attempted, the implementation responds that no such group or event exists. The name appears in test code, but no firing path is provided. There is also no way for users to invoke it. Its existence is limited to documentation.
History of a Description Dating Back to 2000
Its history dates back to July 2000. Vim author Bram Moolenaar added the entry. The description at the time said it occurred when the user pressed CTRL-C. It ended with a note that it was a joke. It reportedly never had functionality from the start. This was more than a year before the release of Vim 6.0.
In August 2001, a smiley was added to the description. It became “When the user hits CTRL-C. Just kidding! :-)”. This was a tonal adjustment, not a functional change. Its character as a joke became clearer. It is a small fix remaining in the documentation history.
In 2013, it was revised to its current form. The condition changed from CTRL-C to pressing the same key 42 times. The smiley was retained. Since then, descriptions to the same effect have been inherited by both Vim and Neovim. The rephrasing after 12 years led to its current recognition.
The inheritance is seen as reflecting a maintenance policy for documentation and test code. Harmless descriptions are more likely to be kept than deleted. It also avoids the effort of excluding them from compatibility checks. As a result, the joke has remained for more than 20 years. An article on documentation maintenance for development tools, Explaining the Technical Relationship Between Next.js Server Actions and RSC, also shows the importance of parsing specification documents.
Extension Showing an Actor’s Image After
42 Presses
In 2022, an unofficial extension inspired by this joke appeared. Its author is developer Mike Smith. Pressing the same key 42 times in insert mode displays an image of actor Samuel L. Jackson. It implements the joke’s condition literally. After 22 years from the idea, it took executable form for the first time.
The implementation has a simple structure that counts user keystrokes. It does not improve any specific editing function. In that it does not contribute to work efficiency, it stands apart from practical extensions. It is strongly entertainment-oriented. Even so, it drew attention as a case of actually making the documented description run.
This extension has not been incorporated into the official implementation. Individual installation is required for use. No firing path has been added to the official autocmd list either. Rather than formalizing the joke, it is positioned as a response by the community. As with surrounding video playback tools, the pattern in which individual ingenuity supplements functionality overlaps with the solution to individual challenges shown by LitPlayer, an SMB/Jellyfin-Compatible Android Video Player.
The Culture of Keeping Jokes and Breathing
Room in Development
Vim’s development history contains occasional descriptions that are not purely utilitarian. A joke left in a corner of the documentation serves to ease maintenance tension. When discovered by beginners, it can also make the tool feel more approachable. It is a way of leaving a human touch in rigid reference documentation.
Similar play is seen in other foundational programs. Easter eggs, hidden commands, displays that change on anniversaries, and other harmless devices have been inherited. The condition for remaining without deletion is that they do not hinder maintenance. They are kept if they do not affect behavior and do not confuse tests. This entry also meets that condition.
On the other hand, from the standpoint emphasizing reference accuracy, some view listing a nonexistent entry as undesirable. There is a risk that jokes will be treated as specifications during automated documentation generation or translation. Beginners may mistakenly believe them. Now that the community has grown, maintaining jokes requires explicit signals. As with OnePlus Europe Exit, New Xteink and AYANEO Models, which reports trends in mobile devices and peripherals, separating fact from observation is also required in documentation.
Editorial Opinion
In the short term, interest in play left in development-tool documentation is expected to grow. Sharing on technical boards and social media may increase, and excavation of similar descriptions may advance. We assess that more new users will read deeply into Vim and Neovim documentation. We also assess that it can be expected to encourage users to create their own extensions.
In the long term, the design philosophy of leaving breathing room in foundational tools is expected to be reevaluated. Recognition may spread that the pursuit of efficiency alone cannot sustain a community. We assess that narrative will become a centripetal force in maintaining continuity. Balancing rigid specifications with cultural memory will become a challenge.
The remaining question is where to draw the line between jokes and specifications. Some view listing nonexistent functionality as confusing for beginners. The danger remains that automatically generated documentation will take jokes literally. How to make community consensus visible is now in question.
References
- “Vim’s UserGettingBored autocmd”, by evanhahn.com via raymii — Lobsters, 2026-09-20T17:18:49.000Z (ARR)
- Source URL: https://evanhahn.com/usergettingbored-vim/
Frequently Asked Questions
- What is UserGettingBored?
- It is a joke entry remaining in Vim's autocmd documentation. It is described as occurring when the same key is pressed 42 times, but it has no firing path and never executes. It exists only in documentation and test code.
- What happens if you try to use it?
- Registering it as an autocmd returns a no such group or event error. It does not work in Vim, Neovim, or Vim Classic. The condition was reproduced only in a 2022 unofficial extension.
- Why has it not been deleted?
- It is seen as remaining because it does not affect behavior or hinder maintenance. Added in 2000, its wording was adjusted and inherited over time. It is maintained as cultural breathing room for the community.
Comments