3 ms·
I don't see there's a reason to use vim locally as other editors are far advanced when vim isn't changing at all. But there's a use on the server side because y
by h1d 7y ago
I don't see there's a reason to use vim locally as other editors are far advanced when vim isn't changing at all.
But there's a use on the server side because you only have vim or emacs there.
- oblio 7y agoAs someone who's been doing sysadmin-ing things for a while... (10+ years) I don't think I've ever seen Emacs installed on any server where it wasn't maybe pulled in as a dependency by something else. Emacs is almost never installed by default, you could instead install micro (https://micro-editor.github.io/ https://micro-editor.github.io/) instead, use normal keybindings, and call it a day :-)
- josteink 7y ago> As someone who's been doing sysadmin-ing things for a while... (10+ years) I don't think I've ever seen Emacs installed on any server Chances are the Emacs-users are working on files on that server remotely via TRAMP, from their nicely and 100% personally customized Emacs-installation. Why bother replicating all that setup on a server when you don't have to?
- oblio 7y agoTrue, but that also means that as someone who regularly SSHes into servers, you don't need to learn anything about Emacs. For local stuff on the servers, vi(m) is always there (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/vi.html https://pubs.opengroup.org/onlinepubs/9699919799/utilities/v...), for remote operation you can use any other editor ranging from Emacs + TRAMP to VS Code + remote extension to ...