When piping the output of eselect --no-color through nopaste script (app-text/nopaste), the text that appears in the past contains the escaping used to set the color to the default: [00mInstalled binutils for target [00mi686-gentoo-freebsd5.4 [00m [00m [00m[1] [00m [00m2.16.1 [00m * [00m [00m [00mInstalled binutils for target [00mpowerpc-unknown-linux-gnu [00m [00m [00m[2] [00m [00m2.16.1 [00m * [00m [00m [00mInstalled binutils for target [00mx86_64-pc-linux-gnu [00m [00m [00m[3] [00m [00m2.16.1 [00m [00m [00m [00m[4] [00m [00m2.16.91.0.4 [00m * [00m [00m this means that the --no-color option is not so likely to be usable for parsing output than one would expect, while it shows up as being "colorless" on terminal. HTH, Diego
Ciaran: We do use SVN instead of CVS, you know? :-P
Wha? Which monkey went and added that? It's silly! Next we'll have to add InArch, InClearCase, InSourceSafe and InGit...
Created attachment 75243 [details] Removes all color codes when option --no-color is used new /usr/share/eselect/libs/output.bash
Comment on attachment 75243 [details] Removes all color codes when option --no-color is used No need for a patch, this one's already tagged as InSVN.
In 1.0.