Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <42461E6F.2020808@endbracket.net> Date: Sun, 27 Mar 2005 12:46:07 +1000 From: Michael Wardle User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: 1.5.13: vim suspend/resume term garbaged References: <42461886 DOT 5060109 AT endbracket DOT net> <42461A5F DOT 9040708 AT endbracket DOT net> In-Reply-To: <42461A5F.9040708@endbracket.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Michael Wardle wrote: > Michael Wardle wrote: > The resumption problem could be a resurfacing of: > http://sources.redhat.com/ml/cygwin/2000-07/msg01091.html > http://sources.redhat.com/ml/cygwin/2001-01/msg00037.html > http://www.cygwin.com/ml/cygwin/2003-05/msg01613.html > > I wonder if it's also related to what's happening with Vim. It seems that if I set CYGWIN=tty, I can resume less processes properly. On the downside, when I quit less by pressing "q", less hangs, so I then have to press CTRL-c to kill it. With CYGWIN=tty, Vim still misbehaves, so I guess the two issues are unrelated. I was going to try CYGWIN=binmode tty, but CTRL-c doesn't even work properly there (for starters, it doesn't cancel the current incomplete command in zsh). :-( -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/