On Tuesday, October 13, 2015 at 9:21:08 PM UTC+2, William Hatch wrote: > I would like to see it fall back on HTTP_PROXY if PLT_HTTP_PROXY is not found. +1
> It is annoying that the cases vary (eg. wget uses http_proxy and https_proxy, > curl uses http_proxy and HTTPS_PROXY), but maybe we could prefer the one in > all caps and fall back on lowercase. To be sure, for HTTP both wget and curl (and not only) agree on `http_proxy`. Before today I had always only seen (on Linux) the lowercase variant, also for other ones (e.g. https://wiki.archlinux.org/index.php/Proxy_settings#Environment_variables, https://askubuntu.com/questions/228530/updating-http-proxy-environment-variable, http://www.cyberciti.biz/faq/linux-unix-set-proxy-environment-variable/). On Tuesday, October 13, 2015 at 9:21:08 PM UTC+2, William Hatch wrote: > It doesn’t use the standard HTTP_PROXY and NO_PROXY from the environment, > since > I want to be able to control the proxies for Racket obviously and separately > from the rest of the environment. But (I'd guess, like William Hatch) most users would want to set those at once. If I were writing a patch and I wanted special proxies for Racket, I'd try to support well common use cases (reading `http_proxy`), and only add extra code for other cases if they're widespread enough. Changing a variable before starting specific command is not hard per se, and it's not hard to have some alias for it: `http_proxy=$PLT_HTTP_PROXY racket ...` -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
