From: "Houder" <houder@xs4all.nl>
To: cygwin@cygwin.com
Subject: Re: Screen crippled by applications using alternative screen
Date: Sun, 27 Apr 2014 09:11:00 -0000 [thread overview]
Message-ID: <cffd4160a0607435e147969246455bcc.squirrel@webmail.xs4all.nl> (raw)
In-Reply-To: <195943e6406b2237c60c2d7df9ddcd11.squirrel@webmail.xs4all.nl>
Hi David Ferenczy,
>> I'm still having issues with applications which use alternative screen
>> for output (LESS, MAN). When I exit that application, its output stays
>> on screen, prompt is displayed over it.
>
> [snip]
>
>> Example steps to reproduce the issue:
>>
>> 1. execute "man grep"
>> 2. scroll down to the end (PAGE DOWN)
>> 3. exit (press Q), result: http://ferenczy.cz/tmp/cygwin/1.png
>> 4. execute "pwd", result: http://ferenczy.cz/tmp/cygwin/2.png
>> 5. clear screen (CTRL + L), result: http://ferenczy.cz/tmp/cygwin/3.png
>>
>> Behavior is the same in plain cmd.exe, Console2 and ConEmu. MinTTY works
>> fine. If I exit MAN on first page (without scrolling), the screen isn't
>> crippled.
>>
>> To reach clean screen I have to repeatedly clear the screen (CTRL + L)
>> until I browse whole MAN output (all pages). ...
>
> Same story here: MinTTY works, Windows Console (cmd.exe): crippled.
>
> My system: XP-sp3, Cygwin: 1.7.29-2 - 32 bits
>
> (behavior Windows Console was not crippled before .28 as far as I can
> remember)
Applied snapshot (i.e. replaced cygwin1.dll) generated by cfg (26/4) ...
@@# uname -a
CYGWIN_NT-5.1 xp 1.7.30s(0.272/5/3) 20140426 17:41:38 i686 Cygwin
@@# man grep
@@# man grep
@@# man grep
@@#
As far as I can tell, the problem has been solved.
Pleasantly surprised ... Thank you Christopher.
Henri
--
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
next prev parent reply other threads:[~2014-04-27 9:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-26 7:38 Houder
2014-04-27 9:11 ` Houder [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-04-25 17:21 Dawid Ferenczy
2014-04-25 17:36 ` Christopher Faylor
2014-04-26 18:06 ` Christopher Faylor
2014-04-26 19:09 ` Dawid Ferenczy
2014-04-26 19:35 ` Dawid Ferenczy
2014-05-03 19:52 ` Dawid Ferenczy
2014-05-03 20:02 ` Christopher Faylor
2014-04-26 18:22 ` Dawid Ferenczy
2014-04-26 19:07 ` Christopher Faylor
2014-04-26 20:16 ` Dawid Ferenczy
2014-04-26 22:45 ` Christopher Faylor
2014-04-26 18:49 ` Dawid Ferenczy
2014-05-01 10:14 ` Maximus5
2014-05-01 22:10 ` Larry Hall (Cygwin)
2014-05-02 5:33 ` Christopher Faylor
2014-05-02 5:37 ` Christopher Faylor
2014-05-02 11:09 ` Maximus5
2014-05-03 5:54 ` Csaba Raduly
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=cffd4160a0607435e147969246455bcc.squirrel@webmail.xs4all.nl \
--to=houder@xs4all.nl \
--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).