When I need to pass through a proxy, links won't take into account the
http_proxy environment variable:

[eric@femto:~]$ grep http_pro .links/links.cfgn
#http_proxy "proxy2.etsit.upm.es"
#http_proxy "proxy.andago.net:3128"
#http_proxy "localhost:3128"

[eric@femto:~]$ export http_proxy="proxy.andago.net:3128"

[eric@femto:~]$ links
http://es.gnome.org/documentacion/articulos/magicpoint/magicpoint/t1.html



                            +------- Error -------+
                            |                      |
                            |  Connection refused  |
                            |                      |
                            |     [ Cancel  ]      |
                            +----------------------+


If I include the variable in $HOME/.links/links.cfg, it works fine:

[eric@femto:~]$ grep http_pro .links/links.cfgn
#http_proxy "proxy2.etsit.upm.es"
http_proxy "proxy.andago.net:3128"
#http_proxy "localhost:3128"
[eric@femto:~]$

[eric@femto:~]$ links http://es.gnome.org/documentacion/articulos/magicpoint/magicpoint/t1.html


                              Magic Point: Presentaciones a la carta (p1 of 3)
   Link: NEXT

                     Magic Point: Presentaciones a la carta

  Alvaro del Castillo San Felix

   acs@barrapunto.com

   Historial de revisiones
   Revision 0.1             19/10/2002             Revised by: acs

Hi Andrei!

Andrei POPESCU wrote:

Thanks a lot for reminding me of these. Manuel A. Fernandez Montecelo
approached me a few weeks because of these, too, but back then I just
found time to work through a few of them.

I've now checked all the remaining ones. At least some of them are
duplicates of bugs against links or links2, others are fixed in
links/links2 in the meanwhile (those should be closed with this mail),
but many seem still present.

Here's my summary (Cc'ed to all mentioned bugs, some of them closed
via -done) of these bugs and what I did so far:

No more present. Closing.

Duplicate of #55425. Forcemerged.

Maybe a duplicate of #509469. Contacting the reporter or the
commenters would likely be the sanes option. Haven't touched it yet.

No more happens in Debian Squeeze. Closing.

Is tagged as unreproducible -> Asking the reporter (which is MIA) or
directly closing. Haven't touched it yet.

Still present. Reassigned.

No more present in Debian Unstable _and_ a duplicate of #108431 which
I can no more reproduce anymore in Unstable. Yay! Reassigned. Closing.

Still present in Unstable. Reassigned.

Of 4 things mentioned in there, 1 is fixed (|), 1 is no more
applicable (h/y), 1 is still there (*) and with the fourth thing, I'm
not sure what he means. The "z" keybinding for "Go back in URL
history" is indeed still present in unstable. Reassigned and
retitled.

Of 3 things mentioned in here, 2 are fixed (languages and codepages
are now a menu), and the third (blank on startup without parameter) is
still present, but likely a wontfix + upstream or such. Reassigned,
tagged and retitled.

Still present. The easiest workaround (and likely that upstream did
that on purpose), is to prepend "./". Reassigned and tagged as wontfix
as this looks like on purpose.

Still present. Reassigned and tagged upstream.

Can't reproduce it anymore and according to the last mail a fix has
been committed upstream:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=144542#11

Closing.

Gah. That sounds like an ugly feature. Not sure what to do. That needs
a non-trivial setup to test. Reassigned. Will maybe test it somewhen
after the freeze.

Still present. Reassigned.

No more present. I just switched to yellow links in the terminal. ;-)
Closing.

Still present. Reassigned.

Still present. Reassigned.

Clearly fixed. Closing.

Still present. Example: /usr/share/doc/developers-reference/index.html
Reassigned.

(I hope none of the bug reporters minds this mass-bug-closing and
-replying. :-)

		Regards, Axel