Post B6Fii1piuLFUzGLjEm by jpmens@mastodon.social
 (DIR) More posts by jpmens@mastodon.social
 (DIR) Post #B6Fii1piuLFUzGLjEm by jpmens@mastodon.social
       0 likes, 0 repeats
       
       "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 😜)
       
 (DIR) Post #B6Fii261viIDnpykee by ed1conf@bsd.network
       0 likes, 0 repeats
       
       @jpmens Hah, I'm a poor archivist/historian of version-particulars and clones. @oclsc tends to be more of an ed(1) historian, so I defer to his expertise.
       
 (DIR) Post #B6Fq5sghGI5TFfRqls by hi@romanzolotarev.com
       0 likes, 0 repeats
       
       correction: #openbsd vi has macros
       
 (DIR) Post #B6Fq5sx0Hf8C4F4sBk by joel@tumfatig.net
       0 likes, 0 repeats
       
       @hi still waiting for #openbsd vi to get UTF-8 and color syntax so I can get rid of vim… :(
       
 (DIR) Post #B6Fq5t8haAUMeWYDQG by ed1conf@bsd.network
       0 likes, 0 repeats
       
       @joel OpenBSD ed(1) should be 8-bit clean, allowing you to edit UTF8 as long as your terminal settings are compatible.  And for syntax highlighting, you can send ranges of lines to be highlighted:$ ed sarc.awk  168  w !bat -l awk  6,$w !pygmentize -l awk(that also works from within vi/nvi if you want)@hi