💾 Archived View for station.martinrue.com › freezr › 3c5d32eeafe9411aa0a1481fe61bce2b captured on 2023-07-22 at 18:34:35. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2023-04-20)
-=-=-=-=-=-=-
Dear Capsulers,
Micro, the editor, is fine to write but not so much for reading, I usually read the drafts in Lagrange with the content already online...
The whole process is a little bit cumbersome... 🫤
What are your strategies to proof-reading your GMI files?
Thanks... 😇
11 months ago · 👍 eph, devyl
I just use emacs for editing and rendering · 11 months ago
@devyl yes I know but I use Lagrange more on the mobile than the computer... So far I came out increasing the size of the terminal font... 🤔 · 11 months ago
Eh, you can open the gemtext with lagrange (or amfora,....) on your local file system!? · 11 months ago
everything i publish is full of typos all the time but i admit it · 11 months ago
Spellcheck lol · 11 months ago
I repeatedly read the paragraphs previously written acouple times during the initial writing in vim and after posting in lagrange. usually the spelling mistakes stick out like a sore thumb, but honestly i've come to the conclusion proof reading isn't worth the energy it takes most of the time. I have accepted my human falibility and expect peoples minds tew bhe entellegint nuff tow full in the gawps. · 11 months ago
vim, hope to spot the errors, git, check on browser (lagrange or elaho) , repeat until correct - alternative could include a local server for dev then push (or rsync) to server when correct - given the small, simple, gmi files i haven't itched enough to spin up a local dev only server yet. · 11 months ago
@acidus I proofread from Android Lagrange... This is not very useful when is time to do some correction later... 🤔 · 11 months ago
No matter how many times I proofread, I can’t see all the errors until after I hit “I publish” · 11 months ago