image does not flush on tmux session

[fm39hz]

• I enabled rendered at cursor, and it work flawlessly when on kitty terminal, but in tmux the image does not flush whatsoever, and will still show the image on every panel then keep spawning this error
  
  
  
• here is my plugin and tmux config:

return {
	{
		"3rd/image.nvim",
		ft = { "markdown", "quarto", "vimwiki" },
		dependencies = { "leafo/magick" },
		opts = {
			integrations = {
				markdown = {
					clear_in_insert_mode = true,
					only_render_image_at_cursor = true,
				},
			},
			html = {
				enabled = true,
			},
			editor_only_render_when_focused = true,
			window_overlap_clear_enabled = true, -- auto show/hide images when the editor gains/looses focus
			tmux_show_only_in_active_window = true,
		},
	},
}

set-option -a terminal-features 'xterm-256color:RGB'
set-option -g status-position top
set -gq allow-passthrough on
set -g visual-activity off
set -ga update-environment TERM
set -ga update-environment TERM_PROGRAM

[3rd]

Wasn't able to reproduce this, do you have anything special / shell wrappers / something different going on?
Kitty + tmux works ok for me.

[uTkArShVeRm4]

Same issue using tmux + kitty, works flawlessly without tmux on wezterm and kitty terminal. I am running it on m1 macbook pro.

[RUGMJ]

Same issue here, running outside of tmux on kitty works fine but with tmux the image stays

[b0o]

Same issue here, works in ghostty (which supports kitty image protocol), but images get stuck with tmux + ghostty.

Update: it seems to not happen in a fresh tmux session, but it was happening in a session I had running for a while. Not sure what was different about that one.

[reynard93]

i got the same issue as well. am using leetcode.nvim and have the questions with images rendered on the side, even after closing the buffer and window it is stuck to my terminal on all the tmux sessions and on all my subsequent windows in the same place

[ficcdaf]

I had this problem and setting tmux_show_only_in_active_window = true fixed it.

[SimonYde]

Any update on this? following the proposed solution by @ficcdaf didn't work for me, as I actually have it set already :/