Drop ProxyMan support for applications using `http_proxy` environment variable
Closed this issue · 1 comments
The major motivation behind creating ProxyMan was handling the cases when applications were not able to function properly, primarily due to
- Not using
http_proxy
environment variable. - Not being launched from
shell
, so variables are set. - Not using system's proxy settings (depending on OS).
However, as of now, almost all tools like git
, npm
, yarn
(#46 ), bower
(#40 ), maven
(#47 ), etc. work well with http_proxy
, the need to configure them manually becomes insignificant. There's just one kind of use case where you'd require a different proxy for git
and http_proxy
, which is a very rare use-case.
I would like to have feedback on if there shall be cleanup in ProxyMan to expect applications to pick up http_proxy
as most of them do.
https://github.com/himanshub16/ProxyMan/tree/v3#how-this-is-going-to-be-different-from-v2
sounds good!
or maybe we can just change Labels of the menu. eg git to git specific