Bug#1064039: Unexpected string when using tmux with rxvt-unicode

[Karine Crévecœur]

Hi,

I tried the patch proposed at:
https://github.com/exg/rxvt-unicode/commit/417b540d6dba67d440e3617bc2cf6d7cea1ed968

It seems to work perfectly.

Cheers

--
Karine Crévecœur

Bug#1064039: Unexpected string when using tmux with rxvt-unicode

[Romain Francoise]

Hi,

On Fri, Feb 16, 2024 at 10:42 AM Karine Crévecœur  wrote:
> I encounter a strange behaviour when I use tmux in rxvt-unicode since
> the version 3.4-1.

Yes, this is a bug in rxvt-unicode's support of OSC commands that is
exposed by tmux 3.4. There's an upstream fix here:

https://github.com/exg/rxvt-unicode/commit/417b540d6dba67d440e3617bc2cf6d7cea1ed968

I'll reassign this bug to rxvt-unicode.

Thanks,
-- 
Romain Francoise 
https://people.debian.org/~rfrancoise/

Bug#1064039: Unexpected string when using tmux with rxvt-unicode

[Karine Crévecœur]

Package: tmux
Version: 3.4-1

Hello,

I encounter a strange behaviour when I use tmux in rxvt-unicode since
the version 3.4-1.

Usually I lanched tmux directly when I start a new rxvt-unicode. Just
after starting, the string "10;rgb:d3d3/d3d3/d3d3]11;rgb://"
is shown at shell prompt.
The same string can be passed to application launch in tmux when I
enlarge or shrink the urxvt window with maximize/un-maximize (I use
openbox as window manager).

So I revert to tmux 3.3a-5 for not be annoyed with this issue.

Notice, this bug appears only with urxvt-unicode (current installed version is
9.31-2).

Cheers.

--
Karine Crévecœur