I think sysadmins should install nano on servers for people to make quick edits. All the commands are along the bottom, so there is no learning curve.

▲

onetom 3 hours ago | parent [-]

or they should just make sure emacs can work with the machine thru ssh, then there is nothing to install ;)

if no ssh, then nano is not a bad option, though i would go with joe (https://joe-editor.sourceforge.io/) which can also show the shortcuts, but much much more powerful, yet it's just a single ~700kbyte exe (or 1.5MB with some optional syntax highlighting grammars and docs)

	▲	opan 37 minutes ago \| parent [-]
		>or they should just make sure emacs can work with the machine thru ssh, then there is nothing to install ;) While (neo)vim doesn't have TRAMP and dired, it has netrw, which does the same stuff (on a basic level). You can do the following to edit a remote file: vim scp://user@hostname/path-to-file-here You can also replace user@hostname with an ssh alias you've configured, which makes it easier to work with multihop ssh and different keys and users. One useful usage of the remote editing is to combine it with opening multiple files to compare two files on different machines: vim -O ~/.config/mpv/mpv.conf scp://htpc/.config/mpv/mpv.conf To browse a directory instead of a specific file, just put the dir instead of a non-dir file and it will open a filebrowser view where you can then pick a file to open. In the above examples, leave off mpv.conf and you'll then be able to pick either your mpv.conf or input.conf or files related to your mpv scripts.