4 ms·
There's a reason I've always removed nano on every system I administer, and have done so for decades: when I first learned of nano, I also learned that it can c
by cesarb 4y ago
There's a reason I've always removed nano on every system I administer, and have done so for decades: when I first learned of nano, I also learned that it can corrupt configuration files where line breaks are significant by hard-wrapping long lines, unless you're very careful to always use "nano -w" instead of just "nano". I believe that this default has changed in a recent version of nano, and even before that some Linux distributions shipped with it set to not hard-wrap by default on a global configuration file, but it's still an unnecessary risk (unless you're really sure that the nano version is recent enough to have the new default, and that you'll never ssh to a machine running an older version of nano).
- themodelplumber 4y agoI accidentally turned this on once, IIRC, and discovered the issue after some shell scripting went off the rails. It was pretty irritating. Still, it led me to a deeper read of the configuration and I ended up enjoying nano more after that. It's come a long way in recent years too.