5 ms·
I'm a Linux/Unix "devop" since 15 years and I still use nano every day or second. It's the default $EDITOR in Debian and derivates and at some machines I did no
by ktpsns 8y ago
I'm a Linux/Unix "devop" since 15 years and I still use nano every day or second. It's the default $EDITOR in Debian and derivates and at some machines I did not consequently set EDITOR=vim.
Congratulations to the developers of nano. It's a timeless modern terminal editor which can be operated by novices as well as experts.
- zitterbewegung 8y agoI absolutely love it when someone makes a tool that "Just works".
- vgy7ujm 8y agoIt sucks ass when you know vim.
- vgy7ujm 8y agoIt really does downvoters.
- sctb 8y agoYou post a lot of snark and then complain about being downvoted for it. If you don't stop we'll ban the account.
- vgy7ujm 8y agoWhat you forgot to mention was that you also banned me from replying for an extended period effectively silencing my voice. I’ll let the readers decide where that kind of behavior lies politically.
- dang 8y agoWe rate-limit accounts when they post too many low-quality comments and/or get involved in flamewars.
- kbd 8y agoHave you considered using sshrc? https://github.com/Russell91/sshrc https://github.com/Russell91/sshrc It lets you take basic shell config with you when you ssh. You could ensure you always had your $EDITOR set to vim and have a basic vim config ready. It's also really nice to take my prompt with me and not have random vanilla/terrible shell prompt that's set on whatever server.
- ktpsns 8y agoWow, this looks like a gem. However, I can imagine many scenarios when this fails if the target machine has a very different software version setup (and older different Linux distribution, for instance). Would require some fine tuning of parameters, but sounds promising!