public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: cyg Simple <cygsimple@gmail.com>
To: cygwin@cygwin.com
Subject: Re: scrolling through history in cygwin terminal window line gets garbled
Date: Sat, 18 Aug 2018 14:17:00 -0000	[thread overview]
Message-ID: <9ee31df5-32e2-22a5-1716-82bc150e6e3e@gmail.com> (raw)
In-Reply-To: <5b7773eb.1c69fb81.5d9c7.2e20@mx.google.com>

On 8/17/2018 9:18 PM, Steven Penny wrote:
> On Fri, 17 Aug 2018 16:36:57, Thomas Wolff wrote:
>> 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.
> 
> This bug has bothered me for years, I would love to see it fixed. Here is a
> simple test case:
> 
>    $ cat ~/.bash_history
>    echo ABCDEF ABCDEF ABCDEF ABCDEF
>    echo 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789
> 
> Result:
> 
>    $ echo ABCDEF ABCDEF ABCDEF ABCDEF        234
> 
> What I tried:
> 
> 1. PS1=%
> 2. "TERM" with no "am" or "bw"
> 3. "TERM" with both "am" and "bw"
> 4. "TERM" with "am" only (couldnt find one with "bw" only)
> 
> If you have a custom terminal that this works with - provide the "infocmp"
> output and I will try it. Note that I am not using Mintty, I am just using
> sh.exe and conhost.exe, so it seems that mintty is not the culprit but
> perhaps
> Cygwin DLL or Readline.
> 

Sorry, I can't duplicate this.  I even tried with conhost and bash -il
in the window and just don't see an issue. My TERM value is xterm and
the data comes from the file /usr/share/terminfo/78/xterm.

-- 
cyg Simple

--
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-18  3:47 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   ` Fw: When " 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 [this message]
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
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=9ee31df5-32e2-22a5-1716-82bc150e6e3e@gmail.com \
    --to=cygsimple@gmail.com \
    --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).