From: Michael Wild <themiwi@gmail.com>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: [Bug] tmux 3.2-0
Date: Wed, 26 May 2021 08:34:26 +0200 [thread overview]
Message-ID: <CAALQ5r=xF_y9cgMn2gRWR4tmvK4TQN-NHYSVx1CepW8NVp=yHg@mail.gmail.com> (raw)
In-Reply-To: <87pmxe1rmk.fsf_-_@Rainer.invalid>
On Tue, May 25, 2021 at 11:02 PM Achim Gratz wrote:
>
> Achim Gratz writes:
> > 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.
> >
> > 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?
>
> Control mode isn't working correctly in Cygwin (compared to the same
> version of tmux in Linux). The expected output never makes it to the
> control mode client.
Hi Achim
Sorry for the mistake with the release number. Should that be a sanity
check in calm?
As for the problem with the control mode: Is there anything I can do?
Like forwarding the problem to upstream? Or do you consider it to be
"unfixable" until Cygwin implements the control mode properly?
Michael
next prev parent reply other threads:[~2021-05-26 6:34 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 [this message]
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='CAALQ5r=xF_y9cgMn2gRWR4tmvK4TQN-NHYSVx1CepW8NVp=yHg@mail.gmail.com' \
--to=themiwi@gmail.com \
--cc=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).