On Thu, Dec 12, 2002 at 07:56:38PM +0100, Robert Land wrote: > On Thu, Dec 12, 2002 at 03:47:29PM +0000, Pigeon wrote: > > > That's a Pigeonism, based on the thought of "bollocks to all the fancy > > stuff". What it does is create a file /tmp/cleandoc.html, based on > > dodgydoc.html but with all the <B>, </B>, <EM> and </EM> removed. > > > > sed - stream editor > > -e - next argument is a string describing some action > > s - substitute > > / - this... > > <B> - ...string here... > > / - ...for this one... > > / - ...oh, it wasn't there, use a null string > > g - do this for every <B> in the line > > What a nice explaination - it does give me some insight > into this topic - thank you very much!
Why, thank _you_! > > > Did you try out another background for COLOR:0? > > > I have gray instead of black but it is overridden! > > > > > > Robert > > > > Just tried blue, and it works. I'm using /etc/lynx.cfg to set options > > globally as I'm the only user and it's easy that way. I've just > > experimented with creating a ~/lynx.cfg or ~/.lynx.cfg, and lynx > > doesn't see that unless I use the -cfg option. Which I find odd. Maybe > > that's what's happening to you? Maybe there's some funny convention > > about the name of a personal lynx.cfg of which both of us are unaware? > > > > Pigeon > > I'm using the same file, blue works fine, but gray and brown > render to black. This is quite puzzling because I do have > 24bit colordepth in this session. Ah. Ug. You're using lynx from within X? This may be related to X colour maps, about which I know nothing. Sorry. I use lynx from the console myself. Having said that, I've just experimented again, and (on the console) brown works but gray doesn't. And I have no idea why! Pigeon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
