public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: mintty 2.7.4
Date: Thu, 09 Feb 2017 19:37:00 -0000	[thread overview]
Message-ID: <d02c301d-b8b4-3c63-00a1-e1c1f886a368@towo.net> (raw)
In-Reply-To: <3e775b3d-2a2a-4cd8-4168-4cc4d502da06@towo.net>

Am 08.02.2017 um 23:51 schrieb Thomas Wolff:
> Am 08.02.2017 um 19:34 schrieb Achim Gratz:
>> Thomas Wolff writes:
>>> Further comments welcome, and it's Achim's turn to provide further
>>> diagnostics input as requested in another mail. It could also be that
>>> screen or tmux simply make invalid assumptions about the setting of
>>> Wraparound modes.
>> That will take a while.  I'll have to set up something at home
>> specifically with the goal of reproducing the error.  At the moment it
>> looks like some sort of race between decisions made at different levels
>> of the stack mintty / tmux / mosh / screen since so far I've not been
>> able to reproduce if I take out one of these.
I’ve installed mosh to see what it actually is.
The man page speaks about speculative local echo which sounds like 
asking for trouble...

Anyway, I could reproduce effects as you described with
mintty – tmux – mosh localhost (no additional screen needed)
And, most interesting for me: the same thing happens in xterm, so it’s 
not a mintty issue :)

> Actually I have found a bug in the combination of auto wraparound mode 
> with scrolling region margins and origin mode.
> Once fixed, that could even affect the issue, we'll see.
The supposed bug mentioned before wasn’t related to scrolling regions.
Instead, I’ve tried to mimick xterm in some obscure border cases, and 
now the vttest case 1 page 3 passes as well.

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

  reply	other threads:[~2017-02-09 19:37 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
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 [this message]
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=d02c301d-b8b4-3c63-00a1-e1c1f886a368@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).