nvi

OpenBSD (as well as the others?) come with pdksh and nvi out of the box.

> probably also switch to fish anyway.

I feel attacked. In all seriousness: so long as you have a POSIX shell available (and set as default), you don't have to use a POSIX shell. I rarely do anything with fish syntax because I mostly use it for the REPL experience.

> Hmm, in this false analogy game, what editor is aligned with korn shell?

vi (not vim), preferably running on OpenBSD :)

It takes a while for the time spent learning emacs/vi to amortise itself. You need to learn the key bindings, the ad hoc scripting language, and the substantial API. And throughout it all, there's the constant temptation to switch to something easier like vscode.

I tried learning to use Org-mode as a Markdown replacement over Doom Emacs. At some point, I switched back to vscode+Markdown and it felt like a breeze. I'm not a SWE, so the payoff would've probably taken too long to happen.

I also tried using the Maxima mode for Emacs as an interactive CAS. The only thing I got was Latex-formatted output and the same Emacs-like key bindings that you get in any terminal emulator. No auto-suggestion/Intellisense to help you navigate and avoid learning the API, so I wasn't overly impressed.

I hate to admit I'm in that camp. Used emacs because it has great support for editing over ssh. When vscode came out with remote connections for ssh and wsl, I switched over. Emacs is a great operating system-I mean editor, but it's pretty hard to extend it to have the feature set of newer editors while maintaining reasonable performance.

Vim bindings are pretty good if you use the nvim plugin in vs code. It's not emulating (n)vim, you need to have the actual nvim installed and it will use that to provide the keyvindings.

I also switched from vs code to doom emacs though, just because I wanted to.

Just use ^D to end, saves you writing here `<<EOM` and EOM there.

I know this is a joke, but I actually used to handwrite all of my programs.

Back then, I would then keypunch them the next time I was on campus and could access a keypunch machine. Writing even a modest 1000 line program was quite a chore because you'd have to carry around a box of 1000 cards and keep them from getting mixed up. Here's a picture of a full 2000 card box[1]; notice how we used to write diagonal lines on the edges of the cards to help put them in order after spilling the box on the floor!

See [2] for a picture of the first kind of keypunch machine I ever used, the IBM 026. The subsequent model, the IBM 029, was much better.

Of course the turnaround time wasn't measured in seconds back then. Once, I was given an assignment that required writing a program in IBM 360 assembler, it was the first time I ever had to write assembly language. With the aid of IBM's excellent manual, IBM 360 Principles of Operation, I hand wrote this program, went to campus to keypunch the program, and turned it in for one of the seven scheduled overnight submissions we were allowed. After around the fifth attempt I was starting the think that I wouldn't get credit for this assignment; miraculously, on my seventh and last submission the program finally worked.

[1] https://upload.wikimedia.org/wikipedia/commons/thumb/8/86/Pu...

[2] https://en.wikipedia.org/wiki/File:Keypunching_at_Texas_A&M2...

The Remote Development extensions being locked away is the kicker for me. Everything else I've been able to find on alternative "markets" (can we just call them repositories? we're all developers here...)