Welcome! I’m Jendia Gammon, Nebula and BSFA finalist author of DUNGEON CRAWL AT THE HAUNTED MALL, THE SECRET OF THE SAPPHIRE SENTINEL, and many other books. Also as J. Dianne Dotson. I am EIC of @starsandsabers and CEO of Roaring Spring Productions, LLC. I’m mom to two teens. I’m also an artist and a science writer. I’m from Appalachia and I live in Los Angeles.
Learn more about me and my work at jendiagammon.com
#Author #Writer #Publisher #Editor #Artist #womeninstem #creative #books
editor
Still using nvi on Slackware.
No plugins. No syntax highlighting. Just speed, predictability, and classic vi behavior, even with multi-GB files.
I wrote a short guide explaining why nvi still matters and how its architecture enables fast, low-memory editing.
📄 https://4c6e.xyz/code_notes.html (NVI Editor Guide)
📄 https://git.sr.ht/~r1w1s1/code-notes/blob/main/notes/NVI_Editor_Guide.txt (plain text)
#slackware #editor #nvi #vi #unix #minimalism
No plugins. No syntax highlighting. Just speed, predictability, and classic vi behavior, even with multi-GB files.
I wrote a short guide explaining why nvi still matters and how its architecture enables fast, low-memory editing.
📄 https://4c6e.xyz/code_notes.html (NVI Editor Guide)
📄 https://git.sr.ht/~r1w1s1/code-notes/blob/main/notes/NVI_Editor_Guide.txt (plain text)
#slackware #editor #nvi #vi #unix #minimalism
TIL again, about low ram footprint editors in OpenSource environments.
In the period where the following commands were valid
ATX3DT
ATA
Such editors were standard. I'm talking about vi. Over extremely noisy POTS lines without error correction, vi was the only editor you could use safely. I remember switching from editing mode to reading mode as frequently as possible, because the 2400 BPS modem from the SR University, had difficulty to keep the line as noise free as possible due to the archaic hardware infrastructure of the phone company.
The editor I'm learning again about is nvi
I'm going to take a deep dive into this, because one thing I love is using the least memory as possible while computing
#vi #nvi #vim #VimMasterRace #editor #SSH #AT #Hayes #OpenSource #programming #Linux #technology
https://4c6e.xyz/code_notes.html
Edited 11d ago
I've been reading since I was 3 years old. Between the ages of 8 and 10, I read more than many average people read in their entire lives. I love reading books. But...
Many current books are written to say two or three things that could be said in three or four pages, and the rest is filler, either due to publisher requirements or to justify the price of the book.
That's when I notice it from the beginning of the book and it makes me lose all desire to read it.
What I do is review the index and skim through the structure of parts and chapters and decide which part I'm really going to read and which I'm going to skip.
For example, I started a book today about the Cold Mountain Poems that has 129 pages in total, and the introduction alone only goes up to page 29. Seriously? Context, history, and who knows what else, but is all that necessary? Well, that happens with almost all the books I've read lately, the newer ones.
The previous one I read had a preface, a prologue to the first edition, a prologue to the second edition, a prologue by the editor, by the brother of the guy who serves coffee at the publishing house, and by the night watchman's cat at the printing press. My brain can't handle that...
People ask why I use Neovim.
It's because of amazing plugins like this ⚡
⌨️ **typr**: Typing practice plugin for Neovim with dashboard.
💯 Supports showing detailed stats & configuration!
⭐ GitHub: https://github.com/nvzone/typr
#neovim #vim #plugin #typing #practice #speed #dashboard #terminal #editor #keyboard #commandline
An introduction to the usage and design of SEdit, the structure editor for Lisp code of Medley Interlisp:
https://files.interlisp.org/medley/docs/internal/sedit/old/intro.tedit.pdf
For more details on the usage and internals of SEdit see (especially code-editing.tedit.pdf):