[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lynx-dev "gettidy.sh": why must one define proxy before evoking Lynx
Re: lynx-dev "gettidy.sh": why must one define proxy before evoking Lynx?
Mon, 16 Aug 1999 09:04:14 +0900 (JST)
> > but HN may still have a problem which has a small programming solution.
> Nobody has ever _asked for_ recognition of arbitrary *_proxy in lynx.cfg.
> It seems all normally used foo_proxy settings are recognized. The
> need for arbitrary_foo just hasn't arisen. The xhttp_proxy, xxhttp_proxy
> etc. are a trick that happens to work (across many lynx versions), nothing
I'm sorry now I even asked, but I do like to ask on the list since others
might benefit or get a hint. I don't "have a problem", but I do have
something I want to do that has a "small programming solution." The point
is though that it is all based on a "trick that happens to work." We,
well, I at least, don't want this kind of stuff going into a general-use
Lynx. If it happened to turn out to be really useful, I would announce it,
but I would strongly oppose any efforts to integrate it into Lynx. I,
and I hope a majority of Lynx users, want a program that follows standards,
not a Netscape clone, or more recently, an MSWORD clone.
Seems to me I heard someone say in a very recent post: "we seem to be
suffering from fidgety programmers." I couldn't agree with you more.