A similar argument is what finally caused the value of the vi family of editors to click in my brain:
They are designed to be fully functional over even the shittiest possible* remote connection. You can’t always count on ctrl, alt, or even the arrow keys being transmitted in a way that is understood by the remote machine.
*Well, I guess the worst possible terminal would be something like an actual teletype, and in that case you’d probably want to fall back to ed or its descendants. To save paper, if nothing else.
Using X forwarding would require you to install big chunks of GNOME or KDE on the server. A better approach is to mount the remote server over SFTP then use KWrite, gedit, whatever, directly on your desktop.
How do you use these when you are connecting via SSH? You enable X forwarding?
It’s fine when you have a graphical environment, but what do you do when you dont have one?
A similar argument is what finally caused the value of the vi family of editors to click in my brain:
They are designed to be fully functional over even the shittiest possible* remote connection. You can’t always count on ctrl, alt, or even the arrow keys being transmitted in a way that is understood by the remote machine.
*Well, I guess the worst possible terminal would be something like an actual teletype, and in that case you’d probably want to fall back to ed or its descendants. To save paper, if nothing else.
ohh yeahh then nano
Using X forwarding would require you to install big chunks of GNOME or KDE on the server. A better approach is to mount the remote server over SFTP then use KWrite, gedit, whatever, directly on your desktop.