X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.8 required=5.0	tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,TW_RX
X-Spam-Check-By: sourceware.org
X-Mail-Handler: MailHop Outbound by DynDNS
X-Report-Abuse-To: abuse AT dyndns DOT com (see http://www.dyndns.com/services/mailhop/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX18Ln2IUnL++vrU9/8ob2hOs
Date: Tue, 14 Feb 2012 20:39:52 -0500
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: rxvt broken in recent snapshots (since cygwin 1.7.10(0.259/5/3))
Message-ID: <20120215013952.GC32195@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <jhe7pn$dj1$1 AT dough DOT gmane DOT org> <4F3AE7A4 DOT 70505 AT cwilson DOT fastmail DOT fm> <4F3AE81B DOT 5010603 AT cwilson DOT fastmail DOT fm>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4F3AE81B.5010603@cwilson.fastmail.fm>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
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 Tue, Feb 14, 2012 at 06:02:51PM -0500, Charles Wilson wrote:
>On 2/14/2012 6:00 PM, Charles Wilson wrote:
>> On 2/14/2012 1:05 PM, Hans Horn wrote:
>>> something in the recent post-1.7.10(0.259/5/3) cygwin snapshots
>>> (20120207..20120214) broke rxvt.
>> 
>> I'll need a few more details than "it broke rxvt".
>
>vis. cgf's reply, never mind...

If the breakage wasn't so obvious, I would have had the same response.

But, really, there is no reason to assume that something is so obvious
as to not provide details.  *Please* when reporting a problem explain
what the problem actually is.

cgf

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