SoylentNews is people
SoylentNews
We make very careful considerations about the interface and operation of the GNU coreutils, but unfortunately due to backwards compatibility reasons, some behaviours or defaults of these utilities can be confusing.
This information will continue to be updated and overlaps somewhat with the coreutils FAQ, with this list focusing on less frequent potential issues.
Good tips and reminders for those who don't work mostly with a CLI (Command Line Interface).
[What has been YOUR biggest CLI gotcha? -Ed.]
This discussion has been archived.
No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
In Tulsa, Oklahoma, it is against the law to open a soda bottle without
the supervision of a licensed engineer.
(Score: 2) by lentilla on Wednesday December 02 2015, @04:31AM
I too will agree. I like ls to use color by default.
My reasoning: a) it adds semantic information to what would otherwise be a homogeneous wall of filenames; b) you can turn it off it you don't like it; and; c) it lets new users know the colorization "feature" exists in an relatively unobtrusive way.
Like many others, I've come across ls colorizing using inappropriate colors for my terminal. (Probably happens more often to me: each new xterm I open uses a different foreground/background color scheme. My monitor looks like a candy shop and I don't loose track of which xterm is which as easily.) Whenever ls' colors don't work I smile and do a quick work-around because I'm grateful for the other 99% of the time they work well.