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:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; q=dns; s=default; b=ky
	RSio/OQzCanr0F8cIV5L2qt2sm6ukRGsusgkzUxNkxLJKlaykot4zFS4iYNlqD3R
	1iR5ew/sXCCpsIhxeUv54TE1dDtXzapaFQnKB4CLMsjMYsG+Gdf/fmHE8z/Jhls/
	p3Q7pjZYxp4t6tgZD+8OszO6KxTMmCkpK0iUa3awY=
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:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; s=default; bh=EYlEfGN/
	Fbf6P97+WsU32rZb2MA=; b=c5tW60kEQLdEMgZ8UMRdR1f/0NLIROjFuc+ab+PM
	2hYRn/gq41S8w9T0zCfry72en49jrOJck0dlBOD8iv/SekHXg5Dl86ZyHSlLCnqr
	9CiuMCDUHZyfuTHbV6T5KrrKfyNAmxsB9cj6D0n3Gc7dpjVBN4+2exPpoZjnywsn
	moQ=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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.2 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2
X-HELO:	mail-vc0-f170.google.com
MIME-Version:	1.0
X-Received:	by 10.220.88.204 with SMTP id b12mr2095815vcm.3.1389994637058; Fri, 17 Jan 2014 13:37:17 -0800 (PST)
In-Reply-To:	<CAF+jOM0T6MqLGnsrEvxhgvczfEFeZ1epzt+inQHKspx_0vdTHA@mail.gmail.com>
References:	<CAF+jOM0T6MqLGnsrEvxhgvczfEFeZ1epzt+inQHKspx_0vdTHA AT mail DOT gmail DOT com>
Date:	Fri, 17 Jan 2014 14:37:16 -0700
Message-ID:	<CAF+jOM2ra8XoVAy8hJ-sZfkX11m2Md8t9sCbX8uj8jMmHE30Zg@mail.gmail.com>
Subject:	Re: Vim under screen screwing up console on close
From:	Aaron Humphrey <alfvaen AT gmail DOT com>
To:	cygwin AT cygwin DOT com
X-IsSubscribed:	yes

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.

On Fri, Jan 17, 2014 at 11:47 AM, Aaron Humphrey <alfvaen AT gmail DOT com> wrote:
> I recently updated my Cygwin64 installation.  I've been using the
> 32-bit version for a while, apparently, but my Setup program for that
> wasn't working, so I switched over to the 64-bit version instead.  As
> such, I'm not sure if this issue is primarily due to running under
> cygwin64, or to having updated versions of the various packages.
>
> 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.
>
> On my 32-bit version, I note that vim under screen doesn't clear the
> window when it exits, but it does scroll the window contents up
> properly when displaying the bash prompt afterwards.  (It does clear
> the window when not running under screen?  Why is that, and is there a
> way to get better control over whether vim clears the screen or not on
> exit?  Just an aside...)
>
> I copied the .minttyrc file (optimized to put my Cygwin window in just
> the right location with just the right size on my second monitor at
> work) from my cygwin32 home directory to my cygwin64 home directory,
> so it's using the exact same settings.
>
> Attached are cygcheck output from my 32-bit and 64-bit installations,
> and my .minttyrc.

--
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

- Raw text -