3 ms·
The irony here is that instead of just unsetting the alias that is proxying `ls` to `ls --color=auto` the solution was to leave the coloring in place but try an
by whalesalad 8y ago
The irony here is that instead of just unsetting the alias that is proxying `ls` to `ls --color=auto` the solution was to leave the coloring in place but try and hack the override env var for defeating that behavior.
ie, `var foo = 1 + 1 - 1` instead of `var foo = 1`
Wouldn't it have been more straightforward to open one's .bashrc/.bash_profile and remove the alias?
- marvy 8y agoSure, but they WANTED colors. The just wanted them to be fast.
- kilianc 8y agoPrecisely. We want colors. We're refined people.
- freedomben 8y agoThe article mentioned that they knew this, but wanted to continue supporting as much color as possible.
- ehsankia 8y agoThe ideal solution would be to have something that disables coloring if there's more than X files. Someone with more linux-fu can probably come up with such a macro.
- laughinghan 8y agoHow is that more ideal than having coloring even on more than X files but still being fast?