* Ian Collier <[EMAIL PROTECTED]> [09-11-07 08:48]: > Sorry if it wasn't clear - I was talking about the defaults for xterm > (in the absence of mutt) in the above sentence.
Yes, I didn't understand that, s/xterm/mutt :^( > > > "mutt -n -F /dev/null" > > > Now you have "normal", ie: no rc file influence. > > That's the idea, yes. we agree here > > > Type ":color normal green black" and now it's green on black. All > > > fine so far. > > > BUT, "normal green black" per the fine manual attaches the meaning of > > "normal" to the "object defined (type of information)" > > Here, "normal" is a technical term which means "any text not covered by > the other color definitions". I'm well aware of what the command does, > but it's not strictly relevant to the colour-switching behaviour. for mutt, yes, but not considering xterm.... > > > It also turns out that specifying "default" *default* for mutt > > > for any one colour switches the whole of mutt from the default > > > white-on-black *default* for xterm, not mutt > > > into black-on-white, except where colour settings have been specified. > > > I find that a bit weird. > > > hopefully explained :^) > > Sorry, I must have missed it. :-( *default* is the definition of mutt's color table, not xterm's, and mutt prevails. better ?? -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org
