Jekyll 2026-08-01T12:49:14+00:00 https://blog.jaysinh.dev/ I am a Full-stack developer by profession, Computer scientist by heart and an Actor by gene. I write mostly on programming topics. Browse through my blog posts to identify my taste of writing. 2017-04-10T12:21:48+00:00 2017-04-10T12:21:48+00:00 https://blog.jaysinh.dev/2017/04/10/goyo-doc-vim-helpfile-for-goyo-plugin <p><img src="https://blog.jaysinh.dev/assets/images/goyo_doc_plugin.png" alt="goyo_doc_plugin" /></p> <h3 id="what-is-goyo">What is Goyo?</h3> <p><a href="https://github.com/junegunn/goyo.vim">Goyo</a> is the vim plugin which allows writers to focus on their writing while they are writing. The plugin deactivates not required fancy windows which are not useful at the time of using vim for writing. It provides certain customizations too.</p> <h3 id="what-is-missing-in-goyo">What is missing in Goyo?</h3> <p>The main problem with <a href="https://github.com/junegunn/goyo.vim">Goyo</a> plugin is that it carries very weak vim specific helpfile. A vimmer is habituated to find help at vim specific helpfile first. After few attempts, I have decided to write a good helpfile for the <a href="https://github.com/junegunn/goyo.vim">Goyo</a> plugin. I am happy to maintain the documentation I have started with the ongoing development of the plugin until the author of <a href="https://github.com/junegunn/goyo.vim">Goyo</a> is providing any concise helpfile for it. The <a href="https://github.com/ultimatecoder/goyo-doc">goyo-doc</a> is not carrying any source of <a href="https://github.com/junegunn/goyo.vim">Goyo</a> plugin, but only contains documentation for the plugin. I am inviting you to propose improvements if you find any.</p> <h3 id="why-i-decided-to-write-a-separate-plugin-for-documentation">Why I decided to write a separate plugin for documentation?</h3> <blockquote> <p>“Documentation is essential. There needs to be something for people to read, even if it’s rudimentary and incomplete.”</p> <p>– <cite>K.Fogel, Producing Open source software</cite></p> </blockquote> <p>I believe the documentation is the most important part of any software. While I was using <a href="https://github.com/junegunn/goyo.vim">Goyo</a> plugin, I found it is missing the vim specific helpfile. I discussed this issue with the author and offered the help for improving on this. You can read further about early discussions <a href="https://github.com/junegunn/goyo.vim/issues/144">here</a>. I didn’t get any positive response from the author so I decided to write and launch vim specific helpfile for this plugin. With this plugin, I am expecting to provide the solution to those users who are more familiar with vim specific helpfile than a Github wiki or README file of any project. Below are the links for downloading and using the plugin.</p> <h3 id="download-links">Download links</h3> <ul> <li> <p><a href="http://www.vim.org/scripts/script.php?script_id=5546">Vimscript</a></p> </li> <li> <p><a href="https://github.com/ultimatecoder/goyo-doc">Github</a></p> </li> </ul> <h6 id="proofreader-farhaan-bukhsh">Proofreader: <a href="https://farhaanbukhsh.wordpress.com/">Farhaan Bukhsh</a></h6> Jaysinh Shukla

Goyo is the vim plugin which allows writers to focus on their writing while they are writing. The plugin deactivates not required fancy windows which are not useful at the time of using vim for writing. It provides certain