X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:to:from:subject:date:message-id:references :mime-version:content-type:content-transfer-encoding; q=dns; s= default; b=wiQrdPT2FCKOuxfQmnAWCT4u8ocAc3U2bfiQVxNRJgEiX9ZPLYAc9 Ug38esabR/akSJvmVLqBbILJM1/9QY6YM0PBwukeoJUcjGgF7xiEI/bN6Kp9+mkd 9ieagctJ2Bh9VZ/9c3/eS8KJd1LWttXU+pQ9F0+RV/U8b1JQSqBFrE= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:to:from:subject:date:message-id:references :mime-version:content-type:content-transfer-encoding; s=default; bh=zDV6rQ3RFp4jguDi1FdXqLhLcuw=; b=wTjTPm1dRWbWljxUxxrj6pGYIfDc Ip/Velog65BcaPWyAlwTk6nf21DQij+odf5fxXdNH08mf2C9In1hOcVftld2cRYS 5+ZqbunDuYXPlKA3VFB9S6lmMhljdl7jdtrY2e9kAg7dNCUPP5bJC7dOQyiODXK7 6A+dmf6DjMh+DDE= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 X-HELO: plane.gmane.org To: cygwin AT cygwin DOT com From: Andrew Schulman Subject: Re: Vim under screen screwing up console on close - cygcheck.out (0/1) Date: Sun, 19 Jan 2014 16:19:25 -0500 Lines: 35 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive: encrypt X-IsSubscribed: yes > > > Simplest way to reproduce is this: run 'screen', then run 'vim', then > > > exit with ':q'. My bash prompt is now on the bottom line of my mintty > > > window, but everything I type, and all output after that, stays on the > > > last line, each line overwriting the previous. Using 'clear', or > > > switching to another screen window and back with Ctrl-A commands, > > > fixes the problem. If I run vim without screen, then it restores the > > > previous window contents after vim exits. This always happens with > > > empty files; it sometimes happens when editing other files, but it > > > doesn't always, and I haven't tried it extensively to try to figure > > > out why. > > > > Looks like vim isn't the only problem here, nor is screen. I was able > > to see some other poor behaviour by looking at a man page and then > > searching for a string which didn't exist--whether running 'screen' or > > not. It displayed "Pattern not found" on the bottom line, which > > caused a bunch of lines to be pushed upward by one, leaving much > > duplication and confusion. (I would attach a screenshot here, but the > > mailer-daemon rejected both png and jpg formats. What does it like, > > gif? bmp? tiff?) I believe I'm using 'less' for my pager, and I can > > see the same thing using less. Less, vim, man...wasn't there another > > issue recently that involved those? Maybe I'll try that snapshot and > > see if that helps with this problem at all. > > I also saw this problem yesterday. I was using screen, but not vim - it > happened in a bash session. I don't know what caused it. After a while > I did something to reconfigure the terminal - I can't remember what, but > maybe I killed the shell or screen session - and it cleared up again. I can only reproduce this bug in screen. So far it happens every time if I start screen automatically from .bash_profile, but not if I wait and start it manually from the shell. I can't figure out yet why that would be. The bug happens in x86 and x86_64. I'm attaching my cygcheck.out, from x86_64. I don't see any obvious problems in it. -- 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