From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: Fw: When scrolling through history in cygwin terminal window line gets garbled
Date: Sun, 19 Aug 2018 16:35:00 -0000 [thread overview]
Message-ID: <6277147e-67be-fa75-6dcd-812bcdd42f1f@towo.net> (raw)
In-Reply-To: <252738798.20180819124725@yandex.ru>
Am 19.08.2018 um 11:47 schrieb Andrey Repin:
> Greetings, surendar jeyadev!
>
> I can confirm this behavior.
How did you reproduce it? I don't.
> Given the position of cut-off, it appears the problem is in wrong character
> width to terminal position count translation.
All the fuzzy test case descriptions in this thread so far were
ASCII-only, so I'm puzzled about your conclusion as I see no
double-width or combining characters involved.
Maybe someone could care to provide a *reproducible test case*.
---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus
--
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:[~2018-08-19 10:19 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 [this message]
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=6277147e-67be-fa75-6dcd-812bcdd42f1f@towo.net \
--to=towo@towo.net \
--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).