it's really fucking annoying when the brainrot hits the maintainers of the tools you're using for more than 30 years.

[malte@anticapitalist.party]

@mawhrin there are good muscle-memory-friendly configs for helix!

[mawhrin@circumstances.run]

@malte unfortunately I have also incorporated in my workflow a number of plugins.

(i'm not saying i won't look, i think i'm just kind of grieving now, as irrational as it sounds.)

[malte@anticapitalist.party]

@mawhrin no, it's very understandable. especially with kind of old-school tools like (neo)vi(m) where a love for the craft and learning things is kind of implied the shock hits a bit harder.

[vatine@mendeddrum.org]

@mawhrin @malte Unfortunately, I do not think that viper-mode supports any vim plugins, but (as someone who prefers old-style vi/nvi to vim, nvi is #1, viper-mode is #2, and vim is the third-best vi, for me and my muscle memory, formed in the late 80s).

[quatermasstools@infosec.exchange]

@mawhrin yup, looks like i’m pinning at 9.0 and recompiling at major os updates.

As a fossil my requirements are minimal, and it will at least give me the chance to kill that god-forsaken command history window.

[art_codesmith@toot.cafe]

@mawhrin @malte "Unix is my IDE..." I weep as I remake all my workflow in Helix and sed.

[resuna@ohai.social]

@davidgerard @lyda @mawhrin

Time to switch to nvi.

[davidgerard@circumstances.run]

@resuna @lyda @mawhrin retvrn to teco

[resuna@ohai.social]

@davidgerard @lyda @mawhrin

vi is basically ed with teco command structure.

[aburka@hachyderm.io]

@malte @mawhrin do tell