From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] tmux 3.2-0
Date: Fri, 14 May 2021 21:10:14 +0200 [thread overview]
Message-ID: <87mtsx6six.fsf@Rainer.invalid> (raw)
In-Reply-To: <announce.CAALQ5rm2xisVPE8WqJOWVxs4o9Qr0Cpcnqx=VybTeyFD005kxA@mail.gmail.com> (Michael Wild via Cygwin-announce via Cygwin's message of "Thu, 6 May 2021 06:54:35 +0200")
Michael Wild via Cygwin-announce via Cygwin writes:
> The following packages have been uploaded to the Cygwin distribution:
>
> * tmux-3.2-0
[nit]
General releases should be numbered starting with 1.
The mosh test suite breaks with this release (the same build tests OK
again with tmux-3.1b), apparently because it is using control mode to
test that zmux actually works and something seems to have changed there
(the command line is 'tmux -C new-session true'). The symptom is that
the whole test just hangs with absolutely no activity until I kill tmux,
at which point the expected output from the control mode session does
seem to appear (except with a return code of 99).
Is the control mode working as intended and if yes, is there a way to
get the old behaviour back that did send the output block to stdout and
then terminated?
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
next prev parent reply other threads:[~2021-05-14 19:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 4:54 Michael Wild via Cygwin-announce
2021-05-14 19:10 ` Achim Gratz [this message]
2021-05-25 20:32 ` [Bug] " Achim Gratz
2021-05-26 6:34 ` Michael Wild
2021-05-26 9:42 ` ASSI
2021-05-31 15:37 ` Michael Wild
2021-05-31 18:15 ` Achim Gratz
2021-06-02 13:22 ` Michael Wild
2021-06-02 17:38 ` Michael Wild
2021-06-03 4:56 ` ASSI
2021-06-05 5:33 ` ASSI
2021-06-05 15:55 ` Achim Gratz
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=87mtsx6six.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).