Github messages for voidlinux
 help / color / mirror / Atom feed
From: leahneukirchen <leahneukirchen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] TMUX inserting terminal color info into prompt
Date: Sun, 18 Feb 2024 16:11:52 +0100	[thread overview]
Message-ID: <20240218151152.E60942428E@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48807@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1304 bytes --]

Closed issue by OliveThePuffin on void-packages repository

https://github.com/void-linux/void-packages/issues/48807

Description:
### Is this a new report?

Yes

### System Info

Void 6.6.16_1 x86_64 AuthenticAMD notuptodate rrrrmmnDFFFFFF

### Package(s) Affected

tmux-3.4_1, rxvt-unicode-9.31_3

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

Whenever attaching to a session, or creating a new session, tmux does not inserts any text into the prompt.

For example the prompt should look like:
```
locolhost%
```

### Actual behaviour

Whenever attaching to a session, or creating a new session, tmux inserts this text into the prompt.

For example this text is inserted after the prompt:
```
localhost% 10;rgb:e500/dd00/eb00]11;rgba:0000/0000/0000/aa00
```
This seems to be the terminal background and foreground color.

Note: Everything works fine on tmux version 3.3a_2.
This also doesn't happen on all terminals (eg, xterm is fine)

### Steps to reproduce

Open a Urxvt terminal ($TERM is rxvt-unicode-256color)
create or attach to a tmux session ($TERM should now be tmux-256color)

On my end, I verified that this bug exists in bspwm and xfce4 and in bash and zsh

      parent reply	other threads:[~2024-02-18 15:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-18  4:42 [ISSUE] " OliveThePuffin
2024-02-18  8:15 ` chrysos349
2024-02-18 15:11 ` leahneukirchen [this message]

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=20240218151152.E60942428E@inbox.vuxu.org \
    --to=leahneukirchen@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /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 NNTP newsgroup(s).