Hallo,
I apologize if this question has been asked already, I found elinks as a
very convenient tool only just recently.
I'm behind firewalls and proxies most of the time so I have to set proxy
definitions.
The common procedure is to set http_proxy etc. with a particular syntax
(note variable names in lowercase), as was established 20+ years ago
with the first cern libwww releases ("I was there at the dawn of the 3rd
age of mankind", sorry, just had to quote this).
What stymies me is why elinks establishes different variable names and
even invented a new syntax for the proxy definition, and it hunts me
every time when I run scripts that I have to maintain 2 different sets
of proxy definitions in a config file.
Why does elinks not honor the usual http_proxy variable, and insist on
using HTTP_PROXY with host:port syntax?
Tschau...Thomas
--
"Do you wanna be a legend or a passing footprint on the sands of time?"
signature.asc
Description: OpenPGP digital signature
-- http://lists.linuxfromscratch.org/listinfo/elinks-users Unsubscribe: See the above information page
