Web lists-archives.com

Re: disable orange progress running apt




On Monday 07 August 2017 08:39:46 Greg Wooledge wrote:

> On Mon, Aug 07, 2017 at 08:05:28AM -0400, Felix Miata wrote:
> > Could this somehow be coming from bash rather than apt?
>
> Nope.
>
> Also while I'm here: the garish colors of apt(8) are not the #1 reason
> I switched back to apt-get(8), but they are #2.  Whoever chose the
> colors clearly doesn't use a terminal with a white background, because
> yellow on white is simply unreadable.

That seems odd, and would tend to make me think of using the educational 
club.

The only machine I have that uses apt as default, is a raspi running 
jessie, and its happy as a clam, either on its full 16 bit color 
framebuffer screen, or on a logged in terminal-4.8 here.

I would first check your "env" output to see if that might be a source of 
odd colors in X. If so, a global grep for the observed string(s) might 
provide a clue for where a color value is miss-set.

The above example machines "env" output contains this:
LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.axv=01;35:*.anx=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.axa=00;36:*.oga=00;36:*.spx=00;36:*.xspf=00;36:

as a single 1433 byte string that your email agent my line wrap, it is 
not here as I send this. There, sometimes only 2 bytes are used to spec 
a color, but I've no clue how to decode the above as I haven't had to 
look into it. Just scanning the above, it looks to be a way of coloring 
a files name in an ls listing, coloring it by its name extension. And 
the colors are 4 bit, which explains why some apps look washed out on 
the raspi's screen. But thats about all I can determine or infer from 
the above.

Colors are often presented as a 24 bit hex string 2 nibbles per color so 
each can have 256 values in terms of it brightness, with the format 
being name of color=RRGGBB with each nibble haveing a value ranging from 
0 to F, so full brightness red s/b FF0000, green 00FF00, etc.  Yellow 
would be something close to FFFF00 for instance.

No clue if this is helpfull but it's at the basics of how most of this 
stuff works.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>