X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-4.8 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <CAK=TapkP4COoL5R5ks5HaC_Wcz_2etUn9Qvr8=uWMu7qqDV+HQ@mail.gmail.com>
References: <CAK=Tapkfg6sv939rx_5MOusQtqB1Me-cgFcE5XmiGDBr24CjpA AT mail DOT gmail DOT com>	<CAHWeT-YexbH7tdBjfjcg-1=XjXTCQnc7GLp2FfBayEJeDDViXA AT mail DOT gmail DOT com>	<CAK=TapkP4COoL5R5ks5HaC_Wcz_2etUn9Qvr8=uWMu7qqDV+HQ AT mail DOT gmail DOT com>
Date: Thu, 5 Apr 2012 12:53:36 +0100
Message-ID: <CAHWeT-Z5mgzn9A8=W0si4C08iGfJBdtLSYzSAZhdT813Hqe-eQ@mail.gmail.com>
Subject: Re: TERM problem with mintty and latest tmux in OpenBSD
From: Andy Koppe <andy DOT koppe AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=UTF-8
X-IsSubscribed: yes
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 30 March 2012 10:03, Michael Simpson wrote:
> On 29 March 2012 06:29, Andy Koppe wrote:
>
>> I don't see any evidence here that this is a problem with mintty
>> rather than OpenBSD's tmux or xterm terminfo entry. Can you try this
>> using Cygwin's xterm?
>
> Cygwin's xterm works as expected

Thanks for checking. Sounds like a mintty incompatibility with xterm
then. I'll need your help to try to narrow down the issue though, as I
haven't got access to an OpenBSD system.

Can you invoke mintty with the --log option for logging output into a
file, do as little as possible to reproduce the problem, and send the
resulting log? The aim here is that I can cat the log file to see the
issue and then try to narrow it down to the problematic control
sequence.

Regards,
Andy

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