This is the mail archive of the
mailing list for the Cygwin project.
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
- Date: Thu, 5 Apr 2012 12:53:36 +0100
- Subject: Re: TERM problem with mintty and latest tmux in OpenBSD
- References: <CAK=Tapkfg6sv939rx_5MOusQtqB1Me-cgFcE5XmiGDBr24CjpA@mail.gmail.com> <CAHWeT-YexbH7tdBjfjcg-1=XjXTCQnc7GLp2FfBayEJeDDViXA@mail.gmail.com> <CAK=TapkP4COoL5R5ks5HaC_Wcz_2etUn9Qvr8=uWMu7qqDV+HQ@mail.gmail.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
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple