Joining #evi irc room from my #c64 ultimate to boost my productivity :) lol

@rachel @mrmasterkeyboard np.

Personally I think editors should be ported to any platform that can physically run them.

• Obviously a 6502-based 8-bit machine can't run evi nor ne, but aside from that there's no legitimate reason an editor needs gigabytes of RAM and multiple 64bit hardware threads.
  • AFAIK ne even started out on the Amiga…

#Editors #ne #evi #Amiga #OpenSource

@rachel it's just sad that neovim (and vim) got enshittfied with SlopCode.

• Not shure if EVi by @mrmasterkeyboard supports Lua like neovim.

Personally I just use ne because it's a good CLI alternative to proprietary editors like Sublime Text…

#neovim #vim #Enshittification #SlopCode #AIslop #Lua #editor #IDE #plugins #ne #evi #Editors #AI #slop

@mrmasterkeyboard @rachel yeah, that's what I've seen so far.

• I think many folks will be fine with just VimScript and a clean and simple, deshittified vim fork…

Stuff like Lua support and plugins are obviously in the 'We have time and spoons to extend and add features' drawer of the 'ideas not decided upon' shelf inside the 'nice to have' closet…

#FLOSS #commentary #NiceToHave #evi #vim #neovim #lua #NiceToHave

@th #EVi!

@BustaMarx

I'm afraid they did. Commit history contains plenty of "claude" and there's this

https://github.com/vim/vim/blob/master/AGENTS.md

replacement fork is called #EVi I believe

Yesterday evening, I replaced fzf & rg with fzy & grep on my system, as well as in EVi. And what should I say? It's snappy, it's accurate. It's without ai slop code. I love it !

#fzf #ripgrep #fzy #grep #EVi

now using #EVi on my 2006 iMac, much better than the built in #VIm for Snow Leopard.

Never mind. Just recognized that ziglang/zig.vim already sets the makeprg haha

#Zig #EVi #Vim

Has anyone played with EVi's (Vim's) makeprg in combination with Zig to utilise the quickfix list? It's not a big thing for me with PHP so far because there's obviously no compiler

#Zig #EVi #Vim

@ki @hell no, otherwise @mrmasterkeyboard wouldn't have to #fork #vim from the last non-#AIslop - #enshittified version…

That fork is called #EVi (Enhanced [?] Vi):
https://codeberg.org/evi-editor/evi

@hell i moved to EVi because vim & neovim got enshittfiied with AIslop-Code.

#EVi #neovim #AIslop #AI #SlopCode #enshittfication cation

#EVi, a non-AI code VIm 9.1.0000 fork that just works. Even on your iBook G3 running 10.4.11.

https://codeberg.org/evi-editor/evi

#UNIX #Apple #iBook #VintageComputing #macOS #Vi #VIm #OpenSource #FOSS #AntiAI #FuckAI #NoAI #Tech #Technology

Alt...

My iBook G3 on Mac OS X 10.4.11 running the EVi editor.

#EVi will take over every UNIX(-like) system and replace VIm's slop, and that's a fact.

https://codeberg.org/evi-editor/evi/

#VIm #UNIX #Tech #Technology

@davidgerard I guess folks will have to fork off pre - AI Slop rsync (if that didn't happen already!) just like pre-Enshittification Vim got forked off as EVi.

#rsync #openrsync #AIslop #AI #slop #Enshittification #vim #evi #SlopCode