public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Csaba Raduly <rcsaba@gmail.com>
To: cygwin list <cygwin@cygwin.com>
Cc: Thomas Wolff <towo@towo.net>
Subject: Re: Fw: When scrolling through history in cygwin terminal window line gets garbled
Date: Mon, 20 Aug 2018 16:47:00 -0000	[thread overview]
Message-ID: <CAEhDDbDJw_LLGFaJ_sN6mtPCa-1Lx_yDnCGfjV1oSzFgiGXoyQ@mail.gmail.com> (raw)
In-Reply-To: <416708705.20180819193131@yandex.ru>

On Sun, Aug 19, 2018 at 6:31 PM, Andrey Repin  wrote:
> Greetings, Thomas Wolff!
>
>>> I can confirm this behavior.
>> How did you reproduce it? I don't.
>
> Exactly as described.
> Start Cygwin using cygwin.bat
> Enter command
> echo ABCDEF ABCDEF ABCDEF ABCDEF
> Enter command
> echo 6789 123456789 123456789 123456789 123456789 123456789 123456789
> Tap twice to pull the first entered command from history.
> Observe part of the second command remaining on the screen.

I couldn't reproduce this, neither with mintty, nor with cygwin.bat
(bash --login -i)
In both cases, the

Windows 7.

$ uname -a
CYGWIN_NT-6.1 assos 2.10.0(0.325/5/3) 2018-02-02 15:16 x86_64 Cygwin

Then I ran Cygwin update, and this happened:

https://imgur.com/FALke6H


Csaba
-- 
You can get very substantial performance improvements
by not doing the right thing. - Scott Meyers, An Effective C++11/14 Sampler
So if you're looking for a completely portable, 100% standards-conformat way
to get the wrong information: this is what you want. - Scott Meyers (C++TDaWYK)

--
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:[~2018-08-19 21:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1372072396.8455798.1534430210374.ref@mail.yahoo.com>
     [not found] ` <1372072396.8455798.1534430210374@mail.yahoo.com>
2018-08-17 15:20   ` surendar jeyadev via cygwin
2018-08-17 16:26     ` Thomas Wolff
2018-08-18 12:36       ` Steven Penny
2018-08-18 14:17         ` cyg Simple
2018-08-18 22:20           ` Steven Penny
2018-08-19  1:27             ` cyg Simple
2018-08-19  9:50               ` Steven Penny
2018-08-19 10:19                 ` cyg Simple
2018-08-19 14:33                   ` Steven Penny
2018-08-20 14:40                     ` cyg Simple
2018-08-19 15:41                 ` Thomas Wolff
2018-08-19 21:04                   ` Steven Penny
2018-08-19 21:45                 ` Jeffrey Walton
2018-08-19 15:17     ` Fw: When " Andrey Repin
2018-08-19 16:35       ` Thomas Wolff
2018-08-20  6:23         ` Andrey Repin
2018-08-20 16:47           ` Csaba Raduly [this message]
2018-08-20 17:11             ` Marco Atzeri

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=CAEhDDbDJw_LLGFaJ_sN6mtPCa-1Lx_yDnCGfjV1oSzFgiGXoyQ@mail.gmail.com \
    --to=rcsaba@gmail.com \
    --cc=cygwin@cygwin.com \
    --cc=towo@towo.net \
    /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).