💾 Archived View for bucareli.online › gemlog › setup.gmi captured on 2022-01-08 at 13:43:40. Gemini links have been rewritten to link to archived content

View Raw

More Information

⬅️ Previous capture (2021-11-30)

-=-=-=-=-=-=-

Writing Process for Gemini

Hi all, this gemlog post has only one purpose: I'd like to know how you do your Gemini writing. First I want to explain my writing process, and I want to learn how I could make it better.

I have a local clone of my server, so if it dies or something goes awry I wouldn't really lose anything I've written. Every time I want to write a new Gemlog, I cd into the gemlog directory and create a .gmi file and edit it in Vim. Do you have any recommendations for how to best setup Vim for Geminitext editing? I often have issues with Vim automatically cutting off my lines when I go over 80 characters by inserting a newline character. How could I improve my .vimrc file so I can keep using Vim for both programming and writing? I have never used Vim for writing anything other than code, and I admit that at times I've had to open my .gmi files in another editor to ensure that the formatting is appropriate, and well, I'd like to avoid that in the future!

After finishing my writing, I use rsync to mirror the changes from my local machine to the Gemini capsule server.

I enjoy doing this process manually, but if any of you have written or know about automation tools for the Gemini content creation or capsule management, I'd love to learn about them. I wonder if there's anything like Tomasino's burrow tool for gopherholes but for Gemini [1].

Github link to the burrow project

Please email me at bucareli@protonmail.com to let me know your thoughts and your writing process!