On Sun, Nov 18, 2012 at 01:41:04PM +0000, Uday S Reddy wrote: >On 10/1/2012 1:18 AM, Christopher Faylor wrote: >> On Sat, Sep 29, 2012 at 11:53:06AM -0400, Ken Brown wrote: >>> On 9/29/2012 11:33 AM, Daniel Corbe wrote: >>>> If this were an environment that I had customized on my own I might >>>> agree with you; however, this is a standard toolkit that I'm working >>>> with and its functionally portable to every platform I've tried to use >>>> so far except for cygwin. >>> >>> And the reason is that this "standard toolkit" uses an obsolete setting >>> of the CYGWIN environment variable. It needs to be updated. >> >> Especially since it had absolutely no business setting the variable to >> begin with. > >I am trying to understand why it is said that emacs-w3m had no business >setting the environment variable. > >Obviously, it was a setting recommended in earlier versions of Cygwin, >and emacs-w3m is setting it for its own sub-processes. Is there a >better way of arranging things?
Whether you understand this or not, once again, the program in question should not have been setting the CYGWIN environment variable like this. If you want to get rid of a warning then take Ken's advice: http://cygwin.com/ml/cygwin/2012-09/msg00381.html We're not changing Cygwin to accommodate somebody else's bad decision. I don't think that this discussion really deserves to be drawn out for months when this is clearly not a Cygwin problem. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
