From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: mintty 2.7.4
Date: Wed, 08 Feb 2017 18:35:00 -0000 [thread overview]
Message-ID: <87r3383515.fsf@Rainer.invalid> (raw)
In-Reply-To: <9c13d3fc-9dbd-f89f-05da-28525e0e16e0@towo.net> (Thomas Wolff's message of "Tue, 7 Feb 2017 21:52:26 +0100")
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.
Are earlier versions of mintty, specifically the last versions of the
2.6 series, still available somewhere? I'm almost certain that these
sort of things didn't happen before October or November last year. Of
course it might have been another update of the other programs involved
as well.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
--
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-08 18:35 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 [this message]
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=87r3383515.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).