no highlight on minimap via ssh

[Kerosin3]

Check list

• I have read through the README (especially F.A.Q section)
• I have searched through the existing issues

Environment info

• OS
  • [X ] Linux
  • Mac OS X
  • Windows
  • Others:

Version info

VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Mar 14 2024 09:05:11) (on a remote)

Question / Problem and steps to reproduce

Hello! Minimap seems to not work via ssh connection, i.e it not highlights neither current line, not current screen in the minimap.
I am connecting to my remote via ssh -X, I'am using just default minimap settings, terminal emulator - kitty@xterm,
Does anyone face such a problem?
I would be grateful for any help in solving this problem.

[ZNielsen]

Can you tell me a bit more about your environment? Local machine, remote machine, version of ssh, etc?

I'm not able to reproduce the issue, minimap over ssh -X works as it should for me.

[Kerosin3]

local machine:

Linux version 6.1.0-17-amd64 (debian-kernel@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.1.69-1 (2023-12-30)
KITTY_SHELL_INTEGRATION=enabled
KITTY_WINDOW_ID=1
ZSH_TMUX_TERM=screen-256color
TERM=tmux-256color
TERM_PROGRAM=tmux
TERM_PROGRAM_VERSION=3.4
TMUX=/tmp/tmux-1000/defa
DESKTOP_SESSION=gnome

ssh -v localhost                                                                                     
OpenSSH_9.6p1 Debian-3, OpenSSL 3.1.5 30 Jan 2024

remote:

Linux version 5.15.0-97-generic (buildd@lcy02-amd64-033) (gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #107-Ubuntu SMP Wed Feb 7 13:26:48 UTC 2024

TERM=xterm
XDG_SESSION_CLASS=user
XDG_SESSION_TYPE=tty

VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Mar 14 2024 09:05:11)
ssh -v localhost
OpenSSH_8.9p1 Ubuntu-3ubuntu0.6, OpenSSL 3.0.2 15 Mar 2022

[Kerosin3]

wow.. was this a misclick?I'm sorry

[ZNielsen]

I'm not able to repro this issue. A couple things to try:

• If you have direct access to the machine in question, try local to see if the problem still occurs (eliminate ssh from the equation)
• Check for any log messages or errors with :mes