X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE
X-Spam-Check-By:	sourceware.org
X-Mail-Handler:	Dyn Standard SMTP by Dyn
X-Report-Abuse-To:	abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User:	U2FsdGVkX18+Rx5knr4izXiuU1lgyKl5
Date:	Sun, 18 Nov 2012 12:48:02 -0500
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Suppressing annoying warnings
Message-ID:	<20121118174802.GA5341@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<86ehllr9mr DOT fsf AT corbe DOT net> <5066FBB3 DOT 409 AT cornell DOT edu> <86y5jsj12o DOT fsf AT corbe DOT net> <50671962 DOT 6020602 AT cornell DOT edu> <20121001001842 DOT GA14567 AT ednor DOT casa DOT cgf DOT cx> <k8aohi$q5i$1 AT ger DOT gmane DOT org>
MIME-Version:	1.0
In-Reply-To:	<k8aohi$q5i$1@ger.gmane.org>
User-Agent:	Mutt/1.5.20 (2009-06-14)
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

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

- Raw text -