Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
Thankfully, ls accepts the option --color=no Yeah, but the command: top --color=no just gives the error message: top: Unknown argument `o' and top is one of the bad examples that forces a color that's in poor contrast with a dark background. In general, the solution probably lies with telling xterm to not do colors. A simple test shows that "xterm --color=no" fails spectacularly. And I wonder why most of the machines don't seem to have a "man xterm" page. I've noticed this before, though I've found it on a few machines. The trouble with finding out how to suppress the colorizing for each individual command is that there are zillions of commands, and each probably has its own idiosyncratic option for controlling colors. This could be a *lot* of work. Maybe I just need to find the source to the old, dumb xterm, and put it into the libraries on the machines that I use. It'd probably be less work than learning how to suppress colorizing in each individual command. - Subcription/unsubscription/info requests: send e-mail with "subscribe", "unsubscribe", or "info" on the first line of the message body to discuss-request at blu.org (Subject line is ignored).
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |