X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: f996b,da5d91a724e73ef8
X-Google-Attributes: gidf996b,public
From: alfie@innocent.com (Gerfried Fuchs)
Subject: Re: Help need
Date: 2000/02/24
Message-ID: <slrn8b9sej.8m.alfie@pc9601.sie.siemens.at>#1/1
X-Deja-AN: 589211911
References: <38B3D099.15480F3@maschendrahtzaun.de>
 <Pine.GSO.4.21.0002232342350.13825-100000@xena>
X-Complaints-To: news@siemens.at
X-Trace: scesie13.sie.siemens.at 951382482 27076 195.1.135.123 (24 Feb 2000
 08:54:42 GMT)
Organization: Siemens AG Austria
User-Agent: slrn/0.9.5.7 (Windows)
NNTP-Posting-Date: 24 Feb 2000 08:54:42 GMT
Newsgroups: alt.ascii-art

Ben Norwood <bdn95@aber.ac.uk> wrote:
> --Ben

 You know that sig-dashes aren't useful that way, don't you? ;)

> [1] Yes, I counted them (I was bored) [2]

 I think of "find /usr/share/figlet -iname *.flf|wc -w" to be more
useful  >;-)

> [2] Nice to see a lynx-friendly site for once...[3]
> [3] <rant> Don't you just HATE going through sites with a huge
> multi-line textual top/LHS banner (table cell) in lynx...even more
> annoying IMHO than 'framed' sites where the frames are labelled
> 'frame1'/'frame2' etc....meanwhile Netscape *still* haven't got the
> hang of css (my site's top banner proves that...) </rant>

 I don't think that lynx should be a standard for text-browsing anymore.
It missed the run, IMHO. Did you give w3m a try yet? It has great
advantages over lynx: It can render tables (which I really blame lynx
for not supporting it - it was sugguested endless times, AFAIK). And it
can render frames, by simply converting the frames to a table *smirks*
 It is also smaller than lynx and start up faster. You can even define a
menu, set the keybindings to your likes.
 You find a link on my page mentioned in the signature. Give it a try -
it surely is worth it! Btw, there is also a binary for windows available
;)

 Have fun!
-- 
Gerfried Fuchs
<URL:mailto:alfie@innocent.com>
<URL:http://alfie.ist.org/alfie/>