HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
junegunn
goyo.vim
Vim Script2013–2026
junegunn / goyo.vim

goyo.vim

:tulip: Distraction-free writing in Vim

16Distinct people
17Mentions
0Explicit recommenders
4.7KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

:tulip: Distraction-free writing in Vim

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year17 dated mentions

Observed mentions: 2013-12-29 05:42:18 UTC to 2026-02-16 13:21:46 UTC.

01232013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20132014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC101
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC101
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC101
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC110
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC000
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC101
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC202
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC211
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC202
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC303
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC202
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC000
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC101

What Hacker News says

17 sources
I've used vim as a prose editor in addition to a code editor for a long time. For me, Goyo was the plugin that always matched what I wanted vim to become when I was in "prose writing mode." https://github.com/junegunn/goyo.vim I combine with limelight.vim: https://github.com/junegunn/limelight.vim This partially simulates the experience/UX of the product iA Writer on macOS or iPad, which is my favorite prose editor, but is proprietary software and doesn't work on Linux. As others mentioned, when in prose writing mode you can also flip on a handful of vim options, I save these as hotkeys in my vimrc. For example, spell checking and line wrapping. In case you're curious: https://github.com/amontalenti/home/blob/master/.vimrc
In Vim-pencil: Rethinking Vim as a tool for writing
With vim, one can go from single setting[1] to something more complex[2] or use one of the available plugins (e.g. typewriter-vim[3] or vim-goyo[4] or vim-focus[5] or Lite-DFM[6] or zen-mode[7] etc.) [1] https://superuser.com/a/368275 [2] https://vitalyparnas.com/guides/vim-typewriter-mode/ [3] https://github.com/logico/typewriter-vim [4] https://github.com/junegunn/goyo.vim [5] https://github.com/merlinrebrovic/focus.vim [6] https://github.com/bilalq/lite-dfm [7] https://github.com/folke/zen-mode.nvim
In Ensō: write now, edit later
I wrote a manuscript in vim a couple Novembers ago, for NaNoWriMo. I used a couple plugins, primarily Goyo [1] to add some margins, but otherwise, yeah, plain vim. I don't think it was really any more productive than my current workflow in Obsidian. Vim keybindings are more useful for editing than for writing (and for editing code in particular, where the changes you're making are much more structured). The extra features afforded by Obsidian don't really make a difference during the actual writing process, but I find they're really useful for outlines and other preliminary work, which is something of a point against a vim-only workflow unless you want to use vimwiki [2] or something. Granted, Obsidian is still a markdown-based tool, so there's still some level of minimalism going on there, but by that point we're really discussing markup
Read the rest
vs word processors, which is its own conversation—and to my mind, a much more important one. I much prefer working in markdown (via pandoc) than in a word processor, because plain text is easy to edit and process through the terminal, and because it lets me separate style choices from content. I find that the markdown live preview that editors like Obsidian and Typora provide (and which vim doesn't) is a really nice compromise between a slick composing experience and the technical affordances of markup. Between that and Obsidian's hypertext features, I think I'll stick with Obsidian for the foreseeable future. [1]: https://github.com/junegunn/goyo.vim [2]: https://vimwiki.github.io/
In Ask HN: Did anyone write a book in Nano?
Two years ago, I did nanowrimo in Vim with a whole suite of plugins: - https://github.com/preservim/vim-pencil - https://github.com/junegunn/goyo.vim.git - https://github.com/junegunn/limelight.vim.git - https://github.com/vimwiki/vimwiki It was fun, and the setup is almost identical to iA Writer which I appreciate. I even had it all on my phone with Termux! Last year I just did it in Markdown in VSCode in "zen mode" which also worked pretty well. It was definitely easier to setup than Vim and had better highlighting of bold/italics/etc.
In Almost monospaced: the perfect fonts for writing
And I don't wanna be that Vim guy, but similarly a mix of these plugins works well for me: https://github.com/junegunn/goyo.vim (distraction free mode) https://github.com/reedes/vim-pencil (better behaviour for writing prose) https://github.com/junegunn/limelight.vim (visual highlighting of current paragraph) https://github.com/plasticboy/vim-markdown (better markdown syntax) https://vim-voom.github.io/ (outliner sidebar) Edit: BTW, for my truly favourite aesthetic experience, I like to pair this setup with a nice dark theme, a high quality font, and cool-retro-term (https://github.com/Swordfish90/cool-retro-term/) emulating an old school CRT. Is this practical or ergonomic? Nope! But I love it!
In GhostWriter is a distraction free Markdown editor
Work notes I have separated by subject across various text files, using ### to delineate a topic. I then use Sublime Text 3 find in all open files (has regex option) as my notes can overlap the way they're separated. Google Keep is what I use when I need to make a fast note to look up something later with no urgency. I'll use PushBullet to push a link or something from my phone to my desktop for when I'm back at that device (I have it setup on my phone/laptop/chromebook). For focused writing, I'll use a vim plugin called Goyo (https://github.com/junegunn/goyo.vim). I think I'm a bit of a mess but this is actually a refinement of systems. One day it'll be perfect!
In Ask HN: How do you keep track of your notes at work?
Fountain lets me screenwrite like how I code, which is awesome. I use Goyo[1] and capslock.vim[2] to reduce distraction and make the capitalization easier. Git in Dropbox works well when only one person is committing. 1: https://github.com/junegunn/goyo.vim 2: https://github.com/tpope/vim-capslock My cowriter uses afterwriting[3] (locally[4]) to view them although we still use unformatted .docx for rough drafts, since he normally writes those and I revise. 3: http://afterwriting.com/ 4: https://github.com/ifrost/afterwriting-labs
In Fountain – A markup language for screenwriting

Showing the 15 most recent of 17 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.