From: ASSI <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: [Bug] tmux 3.2-0
Date: Sat, 05 Jun 2021 07:33:27 +0200 [thread overview]
Message-ID: <87lf7og9js.fsf@Otto.invalid> (raw)
In-Reply-To: <CAALQ5r=3ih5kp_QQK8OPm-qE835yU88RJ2DsmTutembLUgTEZg@mail.gmail.com> (Michael Wild via Cygwin's message of "Wed, 2 Jun 2021 19:38:48 +0200")
Michael Wild via Cygwin writes:
> I just uploaded a patched test version 3.2-1 (yeah, I know, I'm off by
> one with the release number...). Can you give it a go and see whether
> the mosh test suite runs through with it?
No it doesn't and I don't even understand why anybody thinks that would
fix the issue. The output is supposed to go to stdout (that's the sole
purpose of control mode) and it's the fd for the TTY that gets
duplicated there apparently (why that only exists for Cygwin if I'm
reading it correctly is another mystery). So indeed the output now appears on the
terminal, but that's not where it should go when stdout gets redirected
elsewhere.
It _might_ be possible for this particular case that one could open
/proc/${clientpid}/fd/1 and have it do the right thing. If so, then the
call just above that clobbers stdin with the ttyname would probably be
better off as /proc/${clientpid}/fd/0.
Otherwise with the code changes as implemented you'd need to wait for
the AF_UNIX branch by Ken Brown to finally land before tmux works as
intended again.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
next prev parent reply other threads:[~2021-06-05 5:33 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
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 [this message]
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=87lf7og9js.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).