From: ASSI <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: [Bug] tmux 3.2-0
Date: Wed, 26 May 2021 11:42:07 +0200 [thread overview]
Message-ID: <871r9thlw0.fsf@Otto.invalid> (raw)
In-Reply-To: <CAALQ5r=xF_y9cgMn2gRWR4tmvK4TQN-NHYSVx1CepW8NVp=yHg@mail.gmail.com> (Michael Wild via Cygwin's message of "Wed, 26 May 2021 08:34:26 +0200")
Michael Wild via Cygwin writes:
> Sorry for the mistake with the release number. Should that be a sanity
> check in calm?
I personally don't think so, if you want to do a test / pre-release then
starting with a "0" seems netural to me.
> As for the problem with the control mode: Is there anything I can do?
Since it's clearly a regression (on cygwin), it would be a start to
check if any new warnings have popped up during compilation.
> Like forwarding the problem to upstream? Or do you consider it to be
> "unfixable" until Cygwin implements the control mode properly?
I don't know, I haven't looked beyond the fact that
tmux -C new
doesn't give you any of the expected output and indefinitely hangs
(although it seems to process at least some commands that you enter). I
still hope it might just be a misguided #ifdef targeting Cygwin or some
simarly silly mistake.
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
next prev parent reply other threads:[~2021-05-26 9:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 4:54 [ANNOUNCEMENT] " Michael Wild via Cygwin-announce
2021-05-14 19:10 ` Achim Gratz
2021-05-25 20:32 ` [Bug] " Achim Gratz
2021-05-26 6:34 ` Michael Wild
2021-05-26 9:42 ` ASSI [this message]
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=871r9thlw0.fsf@Otto.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).