> pretty much guaranteed to be available on any server I log into
So is nano, the original comment hits the mark, why exactly can't you use a proper code editor via ssh? There's very little reason these days. Haven't used a terminal editor for a decade despite doing tons of work that many would instinctively reach for the same job.
VSCode and pretty much every other equivalent has modal editing if that's the sticking point here.
> nano [pretty much guaranteed to be available on any server]
Having just checked 5 of the servers I'm currently logged into, nano is missing on 3 of them. Although one of those 3 is cygwin which is weird in the first place.
> why exactly can't you use a proper code editor via ssh?
Well, vim is a proper code editor. If you mean VSCode, it's not available everywhere; been at plenty of places where installing/using non-approved software on work machines was forbidden. Also, and this is a minor point, kinda, but using (n)vi(m) remotely rather than VSCode gives me one/many windows fewer to manage on my local end - everything currently lives in iTerm2 and I only have one app to wrangle. Using VSCode would give me another one - unless it can do terminal emulation as well these days?
So is nano, the original comment hits the mark, why exactly can't you use a proper code editor via ssh? There's very little reason these days. Haven't used a terminal editor for a decade despite doing tons of work that many would instinctively reach for the same job.
VSCode and pretty much every other equivalent has modal editing if that's the sticking point here.