public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrew Schulman <schulman.andrew@epa.gov>
To: cygwin@cygwin.com
Subject: Re: Vim under screen screwing up console on close
Date: Sun, 19 Jan 2014 19:35:00 -0000	[thread overview]
Message-ID: <qp9od9dr1iitvlt124ct35og4s1riusq0g@4ax.com> (raw)
In-Reply-To: <CAF+jOM2ra8XoVAy8hJ-sZfkX11m2Md8t9sCbX8uj8jMmHE30Zg@mail.gmail.com>

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



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

  reply	other threads:[~2014-01-19 19:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-17 18:47 Aaron Humphrey
2014-01-17 21:37 ` Aaron Humphrey
2014-01-19 19:35   ` Andrew Schulman [this message]
2014-01-19 21:19     ` Vim under screen screwing up console on close - cygcheck.out (0/1) Andrew Schulman
2014-01-19 21:20     ` Vim under screen screwing up console on close - cygcheck.out (1/1) Andrew Schulman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=qp9od9dr1iitvlt124ct35og4s1riusq0g@4ax.com \
    --to=schulman.andrew@epa.gov \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).