[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: lynx-dev Lynx Windows 4.0? when? - PS

From: mattack
Subject: Re: lynx-dev Lynx Windows 4.0? when? - PS
Date: Fri, 25 Feb 2000 14:22:23 -0800 (PST)

On Fri, 25 Feb 2000, David Combs wrote:
>Seems to me that lynx is a BROWSER.  (and a bloody good one, too)
>All this other junk (well, I don't use it) like news-reading,
>email, etc -- to me, at least, those are just nice little
>conveniences, quick-and-dirty HACKS for when I (or the user)
>is too lazy or the matter at hand is too short, or unimportant,
>to go use a REAL emailer or newsreader, etc.
>Just because M$ (etc) adds all this horseshit to ITS browser,
>as a way of further dominating the world, does not seem
>to me to be relevant to LYNX at all.

Umm, I don't mean to defend the guy (actually I responded long ago 
to him saying that one of the things he wants is, I believe, accomplished
by using the 'screen' program)..

But anyway, doesn't a "web browser" by definition, have to handle 
http, news:, telnet:, gopher:, mailto:, and maybe more types?
Or maybe it's "allowed" to handle those types.

I realize I should go RTFM the RFC, but it seems to me that a lot
of what you are calling "junk" is by definition handled (or handle-able)
by a "web browser"... (and spawning/using external libraries/software is a
good way of "supplying" that functionality)

Note I _AGREE_ that 'using a real newsreader/mail program' when necessary is
a good thing (I still haven't played enough at configuring so I can get
lynx to use pine for 'mailto:'s, but NOT actually spawn pine interactivelly,
but DO put a copy of the message in my sent-mail IMAP box..)..

I guess in a long rambling way (hey I've had jury duty a few days this week,
gimme a break -- actually the jury duty is _fun_ but it starts too early),
I think that your basic statement of "junk" is really part of what a 
"web" browser is, even though us geeks (and I guess most of the general public
nowadays) think that it's http: sites mostly.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]