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:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=O/Iv05+VR90ciatB
	P9DPa24Zh0dUCfIf7Hpxe04PgTfmaUhYYoQqHrshkTXgWzkBDmjPDk3zy1vud4vm
	SSUEzrV1O+BUjtwKnaW32w8uAXxv6VOzmpWH4p0sKbGurbXwMrQQFnOhOAgjDoRb
	23+ADep1pQImFfdrdgonLnMFRfE=
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:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=gMaBek0UWSm8gFPk2c94tj
	zMWVs=; b=qtNeA/oMwywnhDU+dFCZGy8b4en3H/akHoOnWt2Dr3CGBrQ+xcjhXC
	cnb2WeGhiaLVqtlKolAE/Yw9oUgDjZ91VAQteXyFQ+ktUvQOOm7Zf5LwQEQR2NXS
	z4A9oejisSdlP/WYNSljSWB/l7V1VvnorYDnSqI2qGLluXQ4L/oCw=
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-Spam-SWARE-Status:	No, score=-0.2 required=5.0 tests=AWL,BAYES_00,KAM_ASCII_DIVIDERS,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.2 spammy=ups, scroll
X-HELO:	mout.kundenserver.de
Subject:	Re: Fw: When scrolling through history in cygwin terminal window line gets garbled
To:	cygwin AT cygwin DOT com
References:	<1372072396 DOT 8455798 DOT 1534430210374 DOT ref AT mail DOT yahoo DOT com> <1372072396 DOT 8455798 DOT 1534430210374 AT mail DOT yahoo DOT com> <1179039299 DOT 9023936 DOT 1534512963906 AT mail DOT yahoo DOT com>
From:	Thomas Wolff <towo AT towo DOT net>
Message-ID:	<8098c8d2-38ab-0fc0-5eea-8d7009b821e8@towo.net>
Date:	Fri, 17 Aug 2018 16:36:57 +0200
User-Agent:	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version:	1.0
In-Reply-To:	<1179039299.9023936.1534512963906@mail.yahoo.com>
X-IsSubscribed:	yes

Am 17.08.2018 um 15:36 schrieb surendar jeyadev via cygwin:
> I am having a similar issue to that pictorially shown here:
>
>      
> https://unix.stackexchange.com/questions/344502/when-scrolling-through-history-in-cygwin-terminal-window-line-gets-garbled
>
>
> This is new to me as I have been using Cygwin on a Windows 7
>
> machine for several years without encountering this problem.
>
> (Of course, that Cygwin build was from 5 or 6 years back.)
> I just moved to a Windows 10 machine and installed Cygwin from scratch a couple of days back and ran into the issue.
>
> Using the UP arrow to go up the history list, I have no problem till I hit a long command (in the case shown below the problematic command was about 50 characters long). When going one step further up the history list, the leading characters of the long command stay on the command line. I cannot backspace/delete them.
>
> I am using mintty from the standard distribution.
>
> Specific example. I issue a 'history' command to show the
>
> history and then use the UP arrow key to scroll upwards. After 6 Ups, I reach command no. 33 as shown below.
>
> ================================
> sita 41 $  history
>      2  vi .bash_profile
>      3  quit
>      4  eixt
>      5  exit
>      6  histoyr
>      7  history
>      8  vi .bash_profile
>      9  vi .bash_profile
>     10  exit
>     11  history
>     12  cd /usr/share
>     13  ls
>     14  cd
>     15  history
>     16  exit
>     17  history
>     18  history
>     19  exit
>     20  sdafasfas
>     21  history
>     22  cp /usr/share/vim/vim*/vimrc_example.vim ~/.vimrc
>     23  history
>     24  cp /usr/share/vim/vim*/vimrc_example.vim ~/.vimrc
>     25  history
>     26  ls
>     27  cd
>     28  vi .bash_profile
>     29  exit
>     30  history
>     31  exit
>     32  cygcheck -s -v -r > cygcheck.out
>     33  history
>     34  history
>     35  ls
>     36  cd
>     37  pwd
>     38  ls
>     39  history
>     40  exit
>     41  history
> sita 42 $  history
> ================================
>
> Now I move up one more step an get
>
> ================================
> ....
> ....
> 30  history
>     31  exit
>     32  cygcheck -s -v -r > cygcheck.out
>     33  history
>     34  history
>     35  ls
>     36  cd
>     37  pwd
>     38  ls
>     39  history
>     40  exit
>     41  history
> sita 42 $  cygcheck -s -v -r > cygcheck.out
> ================================
>
> which is just what is expected. One more and we get
>
> ================================
>     31  exit
>     32  cygcheck -s -v -r > cygcheck.out
>     33  history
>     34  history
>     35  ls
>     36  cd
>     37  pwd
>     38  ls
>     39  history
>     40  exit
>     41  history
> sita 42 $  cygcheckexit
> ================================
>
> Command 31 (exit) now has the extra characters pre-pending the entry on the history list.
>
> Hitting a return here executes the 'exit', though.
> This seems to work for other commands. It appears as though the characters have no effect. But, they do cause a bit of confusion!
>
> Also I noticed that if I input a really long string for a command, the characters that should be in a new line over write the leading characters of the command -- that is, there is no line feed when the text wraps around.
>
> Would greatly appreciate any help in fixing this.
>
> The 'cygcheck' output is attached.
>
> If you need any further information about the mintty set up, please let me know.
>
> tia.
Please test the following:
* Set you prompt to some basic string, e.g. PS1=%. Does that change 
anything?
* Mintty 2.7.5 changed the default wraparound behaviour to become 
compatible with the xterm default. With setting -o OldWrapModes=true, 
does that change anything?
* Can you cross-test this in xterm?
* Does it happen in a freshly-started mintty? If it only happens later, 
which programs did you run in the meantime?
* Make a screen log demonstrating a minimal test case, please.

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