Normal Mode

@normalmode
277 Followers
64 Following
836 Posts
Don't Stop BelieVim
Websitehttps://normalmo.de
Conway’s Game of Life Vim Macrohttps://normalmo.de/vimlife/
Fibonacci Vim Macrohttps://normalmo.de/posts/recursive-macro/
Pluginshttps://normalmo.de/plugins/
FGA: The gen on the family of 'vi' clones

@jpmens

I recently wrote http://jdebp.info/FGA/original-vi.html and was thinking of doing something like this, to augment it; because Sven Guckes's list (https://guckes.net/vi/clones.html) is definitely dated and incomplete, nowadays.

It does not have #NeoVIM (for obvious reasons). Most lists of clones miss that there are several forks of Bostic #nvi, not least the two forks that are in #FreeBSD and #NetBSD base. Similarly, #DragonFlyBSD has forked nvi2.

@lpar

#vi #VIM #elvis #STEVIE

FGA: You are vanishingly unlikely to be using 'original vi'.

"There are now many vi clones and derivatives to choose from, and I couldn’t find a good comprehensive list of all of them with links, so here’s mine."

https://lpar.ath0.com/posts/2026/05/the-vi-family/

#unix #linux #editing

(and I hold my breath for @ed1conf to release a good comprehensive list of all ed(1) releases with links 😜)

The vi family

The last text editor you’ll ever need to learn.

LPAR
y'>p works too I guess!

RE: https://pouet.chapril.org/@sroccaserra/116566214460290854

For the ex-averse, you can also do this by jumping to the start of the yanked text:

yP'<

or to the end of the putted text (which I think matches the ex-command’s behaviour more precisely):

yP']

What's the lore (if any) behind #Emacs using "yank" for the paste operation and #Vi #Vim using the same word for copy?
Spent the day exploring heirloom-ex-vi (n-t-roff). It's
essentially the cleaned-up 1985 ex/vi 3.7 code, brought
forward by Gunnar Ritter and Carsten Kunze: small, simple,
and very readable — about 25k LOC for the editor itself,
versus 38k for nvi. The memory footprint is lower too,
around 3MB RSS against nvi's 6MB in typical use, and it
feels snappy in daily use.

The limits are by design rather than oversight. Fixed
temp-file blocks and a line-pointer table capped at
LBLKS=900 in the default build give you about 230k lines,
or roughly 30MB of text. Beyond that, you get the classic
"Tmp file too large" — and that's fine, because a screen
editor isn't the right tool for huge files anyway.

Trade-offs worth knowing: no set ruler, single-level
undo, and a hard ceiling on file size. nvi is more
practical for daily work, especially if you live in YAML
where column awareness matters. But heirloom is closer to
the original, and the codebase is genuinely beautiful.
Worth a look.

For anyone curious about the details, I keep a longer note
on heirloom-ex-vi here:

https://repo.or.cz/code-notes.git/blob_plain/HEAD:/notes/Exploring_Heirloom_ex_vi.txt.

Updated today with the LARGEF rebuild instructions for
files beyond the default ceiling.

#vi #unix #suckless #nvi

Wrote a blog post about switching away from the terminal in #Neovim to using #tmux display-popup.

This was a lot less straight forward than expected so thought documenting it would help others in the future.

https://sean.taylormadetech.dev/2026/04/29/tmux-display-popup.html

Sean - Tmux Display Popup

How I've setup tmux to give me a persistent popup terminal with minimal fuss.

I reviewed Linda Lamb’s classic "Learning the vi editor" 5th edition. Still very good:

https://drj11.github.io/2026-04-28/review-learning-the-vi.html

#Unix #vi

Learning the vi editor