#vi — Public Fediverse posts

It's one of those days when I get to say that I've put the missing Canadians in, and located Mr Ed. (-:

#Watcom #OpenWatcom #Commodore64 #retrocomputing #svicc #Canada #Ontario #Waterloo #vi

I decided to make that list anyway.

http://jdebp.info/FGA/vi-family.html

#vi #VIM #NeoVIM #viless #neatvi #nextvi #nvi #elvis #STEVIE

I decided to make that list anyway.

http://jdebp.info/FGA/vi-family.html

#vi #VIM #NeoVIM #viless #neatvi #nextvi #nvi #elvis #STEVIE

I decided to make that list anyway.

http://jdebp.info/FGA/vi-family.html

#vi #VIM #NeoVIM #viless #neatvi #nextvi #nvi #elvis #STEVIE

I decided to make that list anyway.

http://jdebp.info/FGA/vi-family.html

#vi #VIM #NeoVIM #viless #neatvi #nextvi #nvi #elvis #STEVIE

@jpmens

In the spirit of there always being 1 more #vi clone than one thinks, notice that @lpar 's list is lacking Ali Gholami Rudi's #neatvi which is packaged in #pkgsrc and about a decade old now.

https://pkgsrc.se/editors/neatvi

And even then the rule still applies. There's 1 more clone: Sterling Huxley's and Brent Roman's #viless, a quarter of a century old and what #BusyBox supplies.

https://github.com/brentr/viless

#NetBSD #OmniOS

@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

@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

@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

@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

What's the lore (if any) behind #Emacs using "yank" for the paste operation and #Vi #Vim using the same word for copy?

What's the lore (if any) behind #Emacs using "yank" for the paste operation and #Vi #Vim using the same word for copy?

What's the lore (if any) behind #Emacs using "yank" for the paste operation and #Vi #Vim using the same word for copy?

Ah yes, the #vi family—because who doesn't want to juggle arcane incantations just to edit a #text file? 🤹‍♂️ Surely, nothing screams "cutting-edge" like a 50-year-old #editor that's harder to learn than a Rubik's Cube on steroids. 🙄 Enjoy your #retro #tech, hipsters!
https://lpar.ATH0.com/posts/2026/05/the-vi-family/ #editing #programming #hipsters #HackerNews #ngated

Ah yes, the #vi family—because who doesn't want to juggle arcane incantations just to edit a #text file? 🤹‍♂️ Surely, nothing screams "cutting-edge" like a 50-year-old #editor that's harder to learn than a Rubik's Cube on steroids. 🙄 Enjoy your #retro #tech, hipsters!
https://lpar.ATH0.com/posts/2026/05/the-vi-family/ #editing #programming #hipsters #HackerNews #ngated

Ah yes, the #vi family—because who doesn't want to juggle arcane incantations just to edit a #text file? 🤹‍♂️ Surely, nothing screams "cutting-edge" like a 50-year-old #editor that's harder to learn than a Rubik's Cube on steroids. 🙄 Enjoy your #retro #tech, hipsters!
https://lpar.ATH0.com/posts/2026/05/the-vi-family/ #editing #programming #hipsters #HackerNews #ngated

The vi family

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

#HackerNews #vi #family #text #editors #history #coding #community

@rincewind
Zenmeister würden vi benutzen …
#vi #linux #unix

@rincewind
Zenmeister würden vi benutzen …
#vi #linux #unix

@rincewind
Zenmeister würden vi benutzen …
#vi #linux #unix

@rincewind
Zenmeister würden vi benutzen …
#vi #linux #unix

Vi showing off at the beach

Full image in my Pa3on sh0ppe:
https://www.patreon.com/kowachi/shop/september-2024-art-pack-1064888?source=storefront

#arcane #vi #arcanefanart #leagueoflegends

Vi showing off at the beach

Full image in my Pa3on sh0ppe:
https://www.patreon.com/kowachi/shop/september-2024-art-pack-1064888?source=storefront

#arcane #vi #arcanefanart #leagueoflegends

Vi showing off at the beach

Full image in my Pa3on sh0ppe:
https://www.patreon.com/kowachi/shop/september-2024-art-pack-1064888?source=storefront

#arcane #vi #arcanefanart #leagueoflegends

@unionista

Oh man, ich kann mich noch dran erinnern, wie ich 1994/1995 mit pine emails und news gelesen und beantwortet hab.
Pico war mir zu umständilich, also hab ich in pine recht früh auf vi umgestellt.

Auch ich nutze vi / vim zum Dateien bearbeiten immer noch am liebsten.

#linux #vi #pine #foss #gnu

@unionista

Oh man, ich kann mich noch dran erinnern, wie ich 1994/1995 mit pine emails und news gelesen und beantwortet hab.
Pico war mir zu umständilich, also hab ich in pine recht früh auf vi umgestellt.

Auch ich nutze vi / vim zum Dateien bearbeiten immer noch am liebsten.

#linux #vi #pine #foss #gnu

@unionista

Oh man, ich kann mich noch dran erinnern, wie ich 1994/1995 mit pine emails und news gelesen und beantwortet hab.
Pico war mir zu umständilich, also hab ich in pine recht früh auf vi umgestellt.

Auch ich nutze vi / vim zum Dateien bearbeiten immer noch am liebsten.

#linux #vi #pine #foss #gnu

@unionista

Oh man, ich kann mich noch dran erinnern, wie ich 1994/1995 mit pine emails und news gelesen und beantwortet hab.
Pico war mir zu umständilich, also hab ich in pine recht früh auf vi umgestellt.

Auch ich nutze vi / vim zum Dateien bearbeiten immer noch am liebsten.

#linux #vi #pine #foss #gnu

My experiment of using only base install of #OpenBSD in console, has yielded joy and insights. Returned to #Perl, which was my first professional programming language in the 90s, learning how capable #vi is (not vim or neovim) and appreciating #tmux.

I have a cli http get command, but no https yet since the needed Perl modules are not installed. This led to me using FTP to download all the RFCs in txt, and starting an implementation in C.

The OpenBSD man pages are indeed great. Without a browser, I am relying upon them and my Harbeson and Steele C book. I will have to download the openbsd src soon tho, to get some example C code.

I’m not a good C programmer, having to unlearn alot of habits from using higher order languages, and am still exploring good patterns for C functions wrt memory management and error handling. I keep trying to write with mathematical types, not bytes in memory.

But, it’s fun, and I fell aseep last night thinking about my project, and looking forward to finding some time to continue it today.

My experiment of using only base install of #OpenBSD in console, has yielded joy and insights. Returned to #Perl, which was my first professional programming language in the 90s, learning how capable #vi is (not vim or neovim) and appreciating #tmux.

I have a cli http get command, but no https yet since the needed Perl modules are not installed. This led to me using FTP to download all the RFCs in txt, and starting an implementation in C.

The OpenBSD man pages are indeed great. Without a browser, I am relying upon them and my Harbeson and Steele C book. I will have to download the openbsd src soon tho, to get some example C code.

I’m not a good C programmer, having to unlearn alot of habits from using higher order languages, and am still exploring good patterns for C functions wrt memory management and error handling. I keep trying to write with mathematical types, not bytes in memory.

But, it’s fun, and I fell aseep last night thinking about my project, and looking forward to finding some time to continue it today.

My experiment of using only base install of #OpenBSD in console, has yielded joy and insights. Returned to #Perl, which was my first professional programming language in the 90s, learning how capable #vi is (not vim or neovim) and appreciating #tmux.

I have a cli http get command, but no https yet since the needed Perl modules are not installed. This led to me using FTP to download all the RFCs in txt, and starting an implementation in C.

The OpenBSD man pages are indeed great. Without a browser, I am relying upon them and my Harbeson and Steele C book. I will have to download the openbsd src soon tho, to get some example C code.

I’m not a good C programmer, having to unlearn alot of habits from using higher order languages, and am still exploring good patterns for C functions wrt memory management and error handling. I keep trying to write with mathematical types, not bytes in memory.

But, it’s fun, and I fell aseep last night thinking about my project, and looking forward to finding some time to continue it today.

My experiment of using only base install of #OpenBSD in console, has yielded joy and insights. Returned to #Perl, which was my first professional programming language in the 90s, learning how capable #vi is (not vim or neovim) and appreciating #tmux.

I have a cli http get command, but no https yet since the needed Perl modules are not installed. This led to me using FTP to download all the RFCs in txt, and starting an implementation in C.

The OpenBSD man pages are indeed great. Without a browser, I am relying upon them and my Harbeson and Steele C book. I will have to download the openbsd src soon tho, to get some example C code.

I’m not a good C programmer, having to unlearn alot of habits from using higher order languages, and am still exploring good patterns for C functions wrt memory management and error handling. I keep trying to write with mathematical types, not bytes in memory.

But, it’s fun, and I fell aseep last night thinking about my project, and looking forward to finding some time to continue it today.

My experiment of using only base install of #OpenBSD in console, has yielded joy and insights. Returned to #Perl, which was my first professional programming language in the 90s, learning how capable #vi is (not vim or neovim) and appreciating #tmux.

I have a cli http get command, but no https yet since the needed Perl modules are not installed. This led to me using FTP to download all the RFCs in txt, and starting an implementation in C.

The OpenBSD man pages are indeed great. Without a browser, I am relying upon them and my Harbeson and Steele C book. I will have to download the openbsd src soon tho, to get some example C code.

I’m not a good C programmer, having to unlearn alot of habits from using higher order languages, and am still exploring good patterns for C functions wrt memory management and error handling. I keep trying to write with mathematical types, not bytes in memory.

But, it’s fun, and I fell aseep last night thinking about my project, and looking forward to finding some time to continue it today.

@mrv404 Long live #nano!

I’ve been using only Linux for more than ten years now, and as much as possible, I use the terminal — and for editing, I use only nano!

As for #vi, #vim, and similar tools, honestly... even with all these years of #Linux experience behind me, and with this level of knowledge — server administration, scripting, self-hosting — I still can’t use them properly. But personally, I don’t need them anyway.

@mrv404 Long live #nano!

I’ve been using only Linux for more than ten years now, and as much as possible, I use the terminal — and for editing, I use only nano!

As for #vi, #vim, and similar tools, honestly... even with all these years of #Linux experience behind me, and with this level of knowledge — server administration, scripting, self-hosting — I still can’t use them properly. But personally, I don’t need them anyway.

@mrv404 Long live #nano!

I’ve been using only Linux for more than ten years now, and as much as possible, I use the terminal — and for editing, I use only nano!

As for #vi, #vim, and similar tools, honestly... even with all these years of #Linux experience behind me, and with this level of knowledge — server administration, scripting, self-hosting — I still can’t use them properly. But personally, I don’t need them anyway.

@mrv404 Long live #nano!

I’ve been using only Linux for more than ten years now, and as much as possible, I use the terminal — and for editing, I use only nano!

As for #vi, #vim, and similar tools, honestly... even with all these years of #Linux experience behind me, and with this level of knowledge — server administration, scripting, self-hosting — I still can’t use them properly. But personally, I don’t need them anyway.

Lee Tusman wrote a vi clone, in BASIC.

https://leetusman.com/nosebook/yvi

#vi #editor #basic

https://trainingportal.linuxfoundation.org/courses/text-editing-with-vim-sc100

There is a market for this? I love #vi and all, but would never considered that some kind of certification was ever required.

@strigohabro Ich benutze #MacVim.

https://macvim.org

#Editor #Mac #macOS #vi #vim

https://www.europesays.com/es/530849/ Sebastian Berwick se hace con el Tour de Turquía, Tom Crabbe gana la última etapa en Ankara – Esciclismo #ANKARA #ascenso #ataques #berwick #caja #Ciclismo #circuito #conquisto #conservar #cortes #Cycling #Deportes #disputada #domingo #edicion #ES #España #etapa #final #jornada #kilómetro #kilómetros #liderato #llegada #marcada #octava #rga #rural #Salida #sebastian #Seguros #sobre #Spain #Sports #termino #tour #Turquía #ultima #último #urbano #vi

Anyway, we now have a button for the #EVi editor, our anti-AI fork of VIm, that you can use on pages created with EVi which was made and submitted by Hazel! (Check out their site @ https://hazelthats.me)

https://codeberg.org/evi-editor/evi-assets/raw/branch/main/image/88x31.gif

You can find EVi on #Codeberg if you want to try it out: https://codeberg.org/evi-editor/evi

#VIm #Vi #Tech #Technology #Linux #UNIX #OpenSource #TextEditor #AntiAI #FuckAI #NoAI

An intriguing reason for forking #Vim 🧐:

“A Eulogy For Vim”, Drew DeVault (https://drewdevault.com/blog/Forking-vim/).

On HN: https://news.ycombinator.com/item?id=47519308

#VimScript #Vi #AI #LLMs #OpenSource #VimClassic #Forks

Despite using Linux for last 20 years, only thing I can do when some app opens up #vi in terminal...

is to close the terminal.

#EVi update! Please boost!

EVi, our anti-AI fork of VIm which was previously on my #Codeberg account, is now hosted over on our new org "evi-editor" at https://codeberg.org/evi-editor/evi. Please update your fork/clone remotes as soon as possible.

Thanks for your support!

#VIm #Vi #Tech #Technology #Coding #Programming #Linux #UNIX #NoAI #AntiAI #FuckAI

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

Vim Fracturing Along LLM Lines – Is This the Dawn of a New Age of LLM vs. Non-LLM Codebases? https://lowendbox.com/blog/vim-fracturing-along-llm-lines-is-this-the-dawn-of-a-new-age-of-llm-vs-non-llm-codebases/ #Editorial&News #vimclassic #neovim #neovim #evi #vim #vi

SOLUTION: @gumnos came up with the idea of piggy-backing :nohl onto control-l for refresh:

nmap <C-L> :nohl<CR><C-L
imap <C-L> <Esc>:nohl<CR><C-L>a

Hey #vim wizards,

The number one reason I don't use search more freely when editing is that all the highlights triggers my #CDO a little bit, and :nohl is a little clumsy to type in a hurry.

I wanted to map :nohl to an easy-to-press keybind, like ctrl-/, but I can't seem to get it to work.

Any ideas?

" map Ctrl-/ to :nohl
nmap <c-Slash> :nohl<CR>
imap <c-Slash> <Esc>:nohl<CR>a

#vi #vim #nvi #nvim #VimWizards #AskFedi #HiveMind

"If you accidentally end up inside vi, you can quit it by pressing Escape, colon
(:), q (q), bang (!) and pressing return."

#freebsd #ymmd #vi

Haha, the old vi book (Learning the vi Editor, 5th edition) is teaching me new tricks. Or at least, reactivating parts of my brain that had those tricks buried.

:g/^{/-1 p

will display the names of all the functions in this C file... if it's formatted to BSD conventions, with a single «{» on a line of its own between the function prototype line and the body of the function.

(optimisation of ex code possible)
#vi #unix