RE: https://mastodon.online/@rfceditor/116053089319721250
The “Ed” in these RFC announcements indicate with which text editor the document was written.
I think.
RE: https://mastodon.social/@Pikapods/116032800231967704
New business idea for @ed1conf: ed(1) with cloud lock-in.
I got tired of hacking ad-hoc text selection functions, so I wrote edtext: line selection and manipulation using ed address ranges.
https://nedbatchelder.com/blog/202602/edtext
You could always use ed(1) for writing your novel instead:
pure text editing of your .md or .tex files
no need (or really even much ability) to tinker with its configuration
the modal-editing lauded in the post
no elisp or lua to read/modify
no dreaded Emacs pinky-finger, or even remapping required
![]()
While I shared the initial post, it's worth calling out specifically: @rootnode is currently blogging a read-though of the ed(1) source-code and detailing the findings:
https://blog.wollwage.com/2026/20260207-daily-source-reading-ed.html
While the current read-through is only a minimal portion of the way through, it promises to be an interesting series. ![]()
Keeping my streak: next daily source reading is up: https://blog.wollwage.com/2026/20260207-daily-source-reading-ed.html
But you know which $EDITOR was not compromised by state actors? ![]()
https://notepad-plus-plus.org/news/hijacked-incident-info-update/
RE: https://mastodon.me.uk/@emily_s/115935318882732555
I could see ed(1) editing this repo with confidence.
Just had lunch with @yarkot and at one point mentioned the difficulties I was having trying to write an interesting blog post about my holiday Rust+ed(1) adventure. He then said "maybe that's because you're not writing it with ed(1)."
(stunned silence).
🤔
Bond: "Do you expect me to awk?"
Goldfinger: "No, Mr. Bond. I expect you to vi. There is nothing you can awk to me about that I don't already know."
Did you know that POSIX requires AI in vi/ex?
The premier conference for ed(1), the standard text editor. Accessible at 300 baud.
Pronouns: it/its