A catalog of #vi and its descendants:

“The Vi Family”, Mathew (https://lpar.ath0.com/posts/2026/05/the-vi-family/).

Via HN: https://news.ycombinator.com/item?id=48033483

On Lobsters: https://lobste.rs/s/4wi5q4/vi_family

#Vim #Editors #Unix #BSD #TextEditors #ComputerHistory

please find below some interesting resources that relate to how the people's permacomputer project could adapt FORTH for its purposes.

thank you everyone for your thoughtful and constructive suggestions over the last period, as we have been considering FORTH.

it seems the scene is very active, and has lots of ideas.

---

# TI-FORTH Screen Editor

"You will find here a new screen oriented editor for TI-Forth.
For people with other systems, TI-Forth is a fig-forth with some
computer specific extensions. The goal was to write a small
editor with a lot of futures, like autorepeating keys, overtype
and insert, some limited form of cut-and-paste, single-stepping
through source, execution of Forth from editor. Results are
below. Compiled code adds below 2K to system stuff".

https://tuhs.superglobalmegacorp.com/Unix_Usenet/comp.sources.unix/1985-November/004781.html

# eulex

"A straightforward standalone Forth implementation for x86".

https://github.com/davazp/eulex/

https://davazp.net/2012/12/08/eulex-forth-implementation.html

# within the durexforth project

https://github.com/jkotlinski/durexforth/discussions/551

## tt

https://gist.github.com/ekipan/e592bf34c314a260112da08adcff980a

## z

https://gist.github.com/ekipan/28bb4bd609797b6d85c58af45d14ed61

# libforth

"libforth: A small Forth interpreter that can be used as a library written in c99".

https://github.com/howerj/libforth

#FORTH #permacomputing #texteditor #texteditors

Episode 26 of our technology podcast @RuntimeArguments (http://RuntimeArguments.fm) — and it's our one-year anniversary! This one's called "Why You'll Never Switch Editors (And What You're Missing)".

Wolf @YesJustWolf surveys the text editor landscape — Vim, Emacs, VS Code, Helix, and some new AI-powered contenders — while Jim @jammcq defends his 42-year Vim habit (and gets talked into looking at TreeSitter and LSPs).

As always, we want to know what you think:

[email protected]

https://www.buzzsprout.com/2469780/episodes/19034506

#TextEditors #Vim #NeoVim #Emacs #VSCode #HelixEditor #LSP #TreeSitter #AICoding #Podcast #TechPodcast

Tech/software updates

https://fed.brid.gy/r/https://beesbuzz.biz/blog/17465-Tech-software-updates

@SharpCheddarGoblin

On Windows and Linux / BSDs desktops+WINE I use TextPad (sort, diff, grep functions); customisable syntax highlighting included with 3rd party contributions. Not an IDE, but its been my GUI text editor of choice since 1996.

On *nix boxes, I like classic vi(1) (Bostic's nvi) (not vim) and ed(1); the shell is your IDE. There are now at least 2 vim classic hard forks that have ripped the AI slop if you still want vim. See also here

#NoAI #UnplugAI #TextEditors #vi

Over on my other (even sillier) blog, I answered Ellane's questionnaire about how and why I use plain text. In plain text, of course.
Read more: https://danq.me/2026/03/17/questionnaire-plain-text/

#repost #ascii #bbses #nostalgia #textEditors

I've been on #neovim forever, not because it's that amazing but because it's kind of the only option... Atom is dead, VS Code is a semi-proprietary Microsoft AI editor, Zed was potentially interesting for a while but became an AI editor, I never got into EMacs and I don't want a closed source text editor

I'm trying out GRAM now: https://gram.liten.app/, a fork of Zed without the AI and without the hostile ToS. It actually seems pretty nice so far! #texteditors #programming #gram #zed

I was always curious about the Xi editor, sad that it never really took off. Just learned about Lapce, described as a “spiritual successor” to Xi

https://lap.dev/lapce/

https://github.com/lapce/lapce

https://github.com/xi-editor/xi-editor

#Xi #Lapce #TextEditors