From: Daniel Corbe <corbe@corbe.net>
To: cygwin@cygwin.com
Subject: Re: Suppressing annoying warnings
References: <86ehllr9mr.fsf@corbe.net> <5066FBB3.409@cornell.edu>
Date: Sat, 29 Sep 2012 11:33:35 -0400
In-Reply-To: <5066FBB3.409@cornell.edu> (Ken Brown's message of "Sat, 29 Sep	2012 09:46:27 -0400")
Message-ID: <86y5jsj12o.fsf@corbe.net>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.1 (windows-nt)
MIME-Version: 1.0
Content-Type: text/plain
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Ken Brown <kbrown@cornell.edu> writes:

> On 9/28/2012 7:49 PM, Daniel Corbe wrote:
>>
>> I'm using emacs-w3m to render HTML messages in gnus on windows by way of
>> the cygwin w3m port.  It's working, except every time w3m gets run I'm
>> greeted by this warning message:
>>
>> "tty" option detected in CYGWIN environment variable.
>> CYGWIN=tty is no longer supported.  Please remove it from your
>> CYGWIN environment variable and use a terminal emulator like mintty,
>> xterm, or rxvt.
>>
>> emacs is setting the environment variables, not me.  How do I configure
>> cygwin to suppress these errors?
>
> emacs-w3m sets the environment variable.  I just downloaded the source
> for the latter from http://emacs-w3m.namazu.org/ and found the setting
> of the CYGWIN variable in w3m.el.  Just edit that file and remove the
> setting.  Alternatively, it looks like you could solve the problem by
> customizing 'w3m-command-environment'.
>
> This is not a Cygwin problem.  I suggest that you report this to the
> emacs-w3m mailing list.
>
> Ken
>
>

Ken,

I appreciate the offered work-around and I can run with that but I
respectfully disagree with the notion that this isn't a cygwin issue.

I understand the need and the desire to deprecate functionality;
however, plastering warning messages everywhere that could eventually annoy the
end user is the wrong approach to that problem.  

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.  That isn't to mean that it doesn't work but
it certainly doesn't behave properly either.

-Daniel

--
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