[Bug] tmux 3.2-0

Michael Wild themiwi@gmail.com
Mon May 31 15:37:46 GMT 2021


On Wed, May 26, 2021 at 12:08 PM ASSI wrote:
>
> 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.

I just tried the following:

Terminal 1:
$ tmux new -s mysession

Terminal 2:
$ tmux -C attach -t mysession
split-window
split-window -h

And as expected, in Terminal 1 the window got split first vertically,
then horizontally. However, in version 3.1b Terminal 2 was echoing the
commands from Terminal 1. This doesn't happen with version 3.2
anymore. I verified by building 3.2 in WSL 2 (Ubuntu 20.04) and there
the echoing does work.

Just out of curiosity: is this a critical feature for you? E.g. are
you automating tmux with it? Because as far as I understand control
mode is intended for integration with terminal emulators. And so far,
iTerm2 on Mac is the only one implementing the protocol.

Regards

Michael


More information about the Cygwin mailing list