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=CxtgbM1OKFVz2R3V
	UbIJ/ipULts0yzq2RpPJeVdX7lA4PLBUd4C7Pl6MCHVh4NhsS4mNYAJmzm8ftKY8
	T/kWGZGdsfGN55DcmD5ohcyX+O/zlb4lJS6nmFY+jZ7gxtK7UlWL5MdT2kmzyrmu
	CwUJTapUgw5d425cei8Q4FZsctY=
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=7Gkp8/zWyHZ9p5lrBTiv91
	tTlqI=; b=ex7FEs0StoRmyoKvzCsmHusyziX+PVIY1cs1QhvpOKz1iStHpcAJWh
	ZZqaaTO8Jf6P4R4wm8wU1Tkoxz8eqp2opI+JibyEcRCyBF0NSoUR4dea4gYxNAbC
	qVKoTEcNl2iL2Eksma411rWXKvYAGQe32gxdl8qjSYEJ63oHoWZSU=
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-Virus-Found: No
X-Spam-SWARE-Status: No, score=1.6 required=5.0 tests=AWL,BAYES_40,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM autolearn=no version=3.3.2 spammy=Asked, UD:faq.html, popup, retest
X-HELO: mout.kundenserver.de
Subject: Re: [ANNOUNCEMENT] Updated: mintty 2.7.4
To: cygwin AT cygwin DOT com
References: <announce DOT 245a59b4-c8dd-31c0-8f79-3b1c8e28a139 AT towo DOT net> <87vasqrl2a DOT fsf AT Rainer DOT invalid> <c377cada-562c-9a5d-14c3-b1f0b204abd5 AT towo DOT net> <25e79ef3-c0ca-2d9f-7353-413580222412 AT SystematicSw DOT ab DOT ca>
From: Thomas Wolff <towo AT towo DOT net>
Message-ID: <52fb66c3-5dc5-afd7-02bf-acdb0a2a9972@towo.net>
Date: Mon, 6 Feb 2017 20:46:03 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <25e79ef3-c0ca-2d9f-7353-413580222412@SystematicSw.ab.ca>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-UI-Out-Filterresults: notjunk:1;V01:K0:Xw4zhJdfz0w=:H+K+IpSMOKz8cUrBwdJRKC GCRNd5YV1XKb6I2sI/DaX43Q2pdP9WMB5ei9o7Ze/YMFW7oohYqyioEmsnhCpBYqU56n0LYyE cana3uAPPBljbT1pcQ9fmutMmUVXWMYWA48iFjNHNM5F+kYSNPgPGW0V5pdU6uTlUu/31AhRU FRuQ3+LkWc+T+zJ1D8/ljZWjIGzJK9yVKq81Bjip+P/e/JWxg+pzNDVYutuRsfHtbvI3faKuK a0S6cuPALyfqX2eoOMge6j2T8gcRZeFdGQuEpwMkN7ThYlca8kM48QzRuoKaJt3Y08k6t2hg9 +xKOlwkSs8gZlnPPQmmgJetRGQC6xed8vkTjsuI2Xequ4AoWKeBs1wXrkbXs4takz6gzVH9YI l10lEI1GDzDQwhHDIGQBX0DasLTIyn70vcbecUSXraNi7mp1ZNocoQMkYHCGVJDwC9ftbq3LK Bm4CIL4sjr+PNipp0V+/tFstN46/BdIIdGu41UxTWHN4CmAjtKxmSGVBYnWQ3yBq30Iwg+Sxg p8jdjdK/B9LTbp9EspUrusgc5NfxQO8w7dgv252NI4ZgZW/q1veT0Xzsn3ACZdbnMIQEKiISj U0GN0HFZ1fmM5YFXgB8L/ln+rDlDX+FDnEW70cnYcsOX8jShO4SFDpVRBtZmoL8cnDHlVmgSM Bwuzpy8VjaZQ3KFmo7hDXBybiSqzaCqceM2jN7Dof8QsDqcDNQ/jzaPXZV8pxKTLWBqXeuryd SPASMY/i2gzvvPXP
X-IsSubscribed: yes

Am 05.02.2017 um 21:36 schrieb Brian Inglis:
> On 2017-02-05 11:35, Thomas Wolff wrote:
>> Hi Achim,
>>
>> Am 04.02.2017 um 17:13 schrieb Achim Gratz:
>>> Thomas Wolff writes:
>>>> I have uploaded mintty 2.7.4 with the following changes:
>>> Since about November/December last year I'm having problems with
>>> screen and tmux sessions in mintty not correctly refreshing and
>>> leaving garbage characters displayed in the terminal. It seems that
>>> the terminal size is not always correctly reported, especially if
>>> you make the window occupy the left or right half of the screen via
>>> Windows shortcut.
>> Is this within tmux or after leaving tmux (see comment below)? It
>> would be help to cross-test this; if it's mintty, which version
>> would show the behaviour first? What happens in xterm?
>>> Additionally, there seems to be an off-by-one bug when the last
>>> line of the terminal needs to be scrolled up in order to show
>>> content that is longer than the remaining width. This happens when
>>> you for instance recall a long command from history. It's hard to
>>> see what exactoly happens, but it looks like the one character too
>>> many gets printed (and wraps onto the next line) before the whole
>>> terminal window gest scrolled up and the rest of the command gets
>>> printed in the line below the single wrapped character. That
>>> remainder is in various states of disarray, showing both remnants
>>> from the original prompt on the last line (now three lines up),
>>> empty /spaces where there should have been characters from the
>>> command and then of course parts of the command.
>> This might be related to some issue with terminal geometry as
>> perceived by the shell (see
>> https://github.com/mintty/mintty/issues/377#issuecomment-137728631).
>> Have you checked that? Recently changed your prompt? Try with basic
>> prompt (PS1="\w> ") please.
> Thanks for supporting and enhancing mintty to be even better in
> Cygwin, and able to be used as a console for other environments.
>
> The test below may be relevant to the above problem, or may be
> unrelated.
> Running vttest 2.7 (20140305)
> http://invisible-island.net/vttest/vttest.html
> updated by and used by xterm maintainer for testing.
>
> Test 1. Test of cursor movements screens 3 80 col mode and 4 132 col
> mode gives results looking like below ...
I was aware this test fails, but save any related bug reports so far I 
had assumed it would not be relevant for applications...
Actually, urxvt (rxvt-unicode as invoked on cygwin) fails the same test 
in the same way, so
@Achim: can you please retest with urxvt, for some additional diagnostic 
information?
Actually, also xterm would fail this test if vttest would not disable 
Reverse Wraparound mode initially.
It also enables Wraparound mode which again affects the test case. 
Mintty does not support Reverse Wraparound mode disabling, it's always 
implicitly enabled. I could try to change that, however, I'm not sure 
yet that's really the cause.
Also, the "proper" way to handle wraparound situations (in the 4 
combinations of the 2 modes) is not completely clear, and Reverse 
Wraparound is an xterm specific mode which did not exist on the DEC 
terminals. See some links for reference:
bash - An obscure one: Documented VT100 'soft-wrap' escape sequence? - 
Stack Overflow 
<http://stackoverflow.com/questions/31360385/an-obscure-one-documented-vt100-soft-wrap-escape-sequence#31360700>
http://stackoverflow.com/questions/31360385/an-obscure-one-documented-vt100-soft-wrap-escape-sequence#31360700
XTerm – Frequently Asked Questions (FAQ) 
<http://invisible-island.net/xterm/xterm.faq.html#vt100_wrapping>
http://invisible-island.net/xterm/xterm.faq.html#vt100_wrapping
VT100 Termcap Entry (CENG 455) 
<http://www.pitt.edu/%7Ejcaretto/text/cleanup/vt100-termcap.html>
http://www.pitt.edu/%7Ejcaretto/text/cleanup/vt100-termcap.html

> It may also be useful if mintty had some character hex value box
> display mode switch to display the actual codes at each visual
> position, or maybe a font used to display the character hex value in
> a box, often used in fonts as glyphs for non-printing control
> characters and those in the Private Use Area, in which case that could
> perhaps be added to the mintty package for use in testing.
> I have been searching for such a font with no success so far.
Hmm, I don't see how that's related to this issue, but it might be a 
nice feature.
Like my text editor, mined, actually does: inform about current 
character code and name (and CJK details if desired).
I could imagine to have a mode (switchable by context menu) that shows 
this information in the window title bar, to avoid the effort of 
handling a popup box.

------
Thomas

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