Command for setting user vars is being printed before each command

alioguzhan commented 6 months ago

What Operating System(s) are you seeing this problem on?

Linux X11

Which Wayland compositor or X11 Window manager(s) are you using?

Kde Plasma 5.27.10 XDG_SESSION_TYPE=x11

WezTerm version

20240203-110809-5046fc22

Did you try the latest nightly build to see if the issue is better (or worse!) than your current version?

No, and I'll explain why below

Describe the bug

If I spawn a new terminal from inside a tmux session: all my commands get a prefix (a command is printed, specifically):

I can see this is coming from: https://github.com/wez/wezterm/blob/main/assets/shell-integration/wezterm.sh#L435

The weird part for me was, that even if I open another terminal (Tilix) I see these WezTerm logs.

But not sure if this is an issue on the WezTerm side or Tmux or Neovim. Any guidance or help would be great.

To Reproduce

Open WezTerm
create a Tmux session
open nvim (nvim --clean)
create a terminal buffer (:terminal)
run any command

Configuration

local wezterm = require 'wezterm'

return {
  font = wezterm.font("JetBrainsMono Nerd Font"),
  font_size = 12.0,
  color_scheme = "Tokyo Night",
  audible_bell = "Disabled",
}

Expected Behavior

No response

Logs

No response

Anything else?

No response

GusJelly commented 3 months ago

I also have this issue, I am running on Hyprland so I don't think it has anything to do with the display server. It probably has to do with some interaction between wezterm and neovim.

alioguzhan commented 3 months ago

Either it is because wezterm / tmux or we both have the same plugin that causes this... @GusJelly

I still couldn't find the cause of this.

GusJelly commented 3 months ago

@alioguzhan I think it's a weird interaction between the user vars that wezterm sets, tmux and neovim. It's not caused by a plugin since it still happens with nvim --clean.

I'm working right now so later today I will take some time and try to figure this out.

GusJelly commented 3 months ago

After looking into what was happening, it seems to me that this is due to a bug between neovim and tmux. For some reason they are not ignoring the \033]1337 when using the neovim terminal, I'm sorry but I'm not familiar with the code that tmux and neovim use for their terminals.

rockyzhang24 commented 3 weeks ago

This issue still persists. I am using the nightly wezterm and nightly Neovim.

wez / wezterm