From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: mintty 2.7.4
Date: Sun, 05 Feb 2017 20:36:00 -0000 [thread overview]
Message-ID: <25e79ef3-c0ca-2d9f-7353-413580222412@SystematicSw.ab.ca> (raw)
In-Reply-To: <c377cada-562c-9a5d-14c3-b1f0b204abd5@towo.net>
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 (shortened lines to 71
characters to avoid wrap issues and fixed content to match display
results):
Test of autowrap, mixing control and print characters.
The left/right margins should have letters in order:
M m
N
n
O o
P p
Q q
R
r
S s
T t
U u
V
v
W w
X x
Y y
Z
z
Push <RETURN>
Unfortunately most of the test documentation is in the source as tables.
If you find vttest useful, it might be worth adding to the mintty
package as a test program, where you or others could ask users with
problems to run specific tests, as xterm does.
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.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
--
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:[~2017-02-05 20:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-27 21:45 Thomas Wolff
2017-02-04 16:13 ` Achim Gratz
2017-02-05 18:36 ` Thomas Wolff
2017-02-05 18:55 ` Achim Gratz
2017-02-06 19:16 ` Achim Gratz
2017-02-06 19:29 ` Thomas Wolff
2017-02-05 20:36 ` Brian Inglis [this message]
2017-02-06 19:46 ` Thomas Wolff
2017-02-07 1:03 ` Doug Henderson
2017-02-07 7:31 ` Brian Inglis
2017-02-07 20:52 ` Thomas Wolff
2017-02-08 2:17 ` Brian Inglis
2017-02-08 18:35 ` Achim Gratz
2017-02-08 22:52 ` Thomas Wolff
2017-02-09 19:37 ` Thomas Wolff
2017-02-09 19:42 ` Achim Gratz
2017-02-09 20:09 ` Thomas Wolff
2017-02-07 21:00 ` diagnostic character info (Re: [ANNOUNCEMENT] Updated: mintty 2.7.4) Thomas Wolff
2017-02-09 19:38 ` Thomas Wolff
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=25e79ef3-c0ca-2d9f-7353-413580222412@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).