Re: TERM problem with mintty and latest tmux in OpenBSD

2012-04-05 Thread Andy Koppe
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 Tha

Re: TERM problem with mintty and latest tmux in OpenBSD

2012-03-30 Thread Michael Simpson
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 Centos 5.8, fedora 17, konsole etc work as expected mike

Re: TERM problem with mintty and latest tmux in OpenBSD

2012-03-28 Thread Andy Koppe
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 appe

TERM problem with mintty and latest tmux in OpenBSD

2012-03-22 Thread Michael Simpson
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