deproxifying lynx?

[pawaan]

thanks for guidance
I'd like to know about something related
if I set in my profile
http_proxy=http://127.0.0.1:8118/
HTTP_PROXY=$http_proxy
export http_proxy HTTP_PROXY

and decided to deproxify lynx surfing without having to relogin , what's to be done ?
the [ export no_proxy="localhost" ] doesn't work.

[ocicat]

Welcome pawaan to our forums.

Most members here use the archives for searching/researching topics. We find that keeping threads on a single subjects makes this process simpler, so we ask all members to keep this in mind. If in the course of conversation you would like to discuss an unrelated topic, please start a new thread. This is covered in the forum rules.

[pawaan]

Thanks.
I'll keep the rule in mind.

[jggimi]

In both bourne and C shells, use "unset <variable>"

[pawaan]

Thanks you.It works.
if I want all open xterm sessions with undergoing processes to learn and apply the new change (unsetting http_proxy) ?
Please consider :
multiple wget mirroring xterm sessions behind proxy and would want to continue mirroring without proxy , without interrupting those processes
Is there a way to extend the unset command to include other running xterms ?

[jggimi]

Each xterm -- and each shell -- has its own environment. While there might be some third party software solution, it may be significantly easier to merely set the value when you need it. For example, you might use "lynx" when you don't need a proxy, and create a simple shell script, or shell function (depending on your preferred shell) that sets your environment variable for the command when you need it. For example, here's a simple script that might be chmod 700 or 755 and reside in a directory in your $PATH, such as in $HOME/bin. You might call this file "lynxproxy" or some other name, then, just use it instead of lynx when you want to use a proxy. You could, of course, do the reverse and unset the variable instead of setting it as shown here. In that case, you might pick a different name, such as "lynxclear". The choices are endless.

#!/bin/sh
env HTTP_PROXY=http://127.0.0.1:8118/ lynx $*

Warning - I haven't tested this, and may have made an error when I typed.