X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: References: Date: Thu, 29 Mar 2012 06:29:36 +0100 Message-ID: Subject: Re: TERM problem with mintty and latest tmux in OpenBSD From: Andy Koppe To: cygwin@cygwin.com Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On 22 March 2012 21:43, Michael Simpson wrote: > Hi there > > using MinTTY-1.0.3-1 > cygwin-1.7-11-1 > tmux on OpenBSD -current > > > When reattaching tmux (tmux attach) there was a series of 3 sets of > semi-colon separated numbers appearing after the ksh prompt. > This behaviour in tmux only appeared after recent changes to tmux in OpenBSD > This behaviour only disappeared when TERM in .bashrc was set to cygwin > from xterm > > a TERM of xterm does not cause this problem in CentOS5.8 or Fedora 17 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? 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