When vim-tabby is installed - garbage sometimes appears in the vim editor when the file is opened

[yurivict]

For example, when I try to create the file 'x' with the 'vim x' command the file appears with already present garbage string like this:
^[[2;2R^[[3;1R^[[>1;115;0c^[]10;rgb:fcfc/fcfc/fcfc^G^[]11;rgb:2323/2626/2727^G

vim-9.1.158 is used configured with the huge option for installed features.
FreeBSD 14.0

[Geremia]

I get this issue, too, with vim 9.1 (2024 Jan 02, compiled May 26 2024 12:27:33) with recent vim-plug and vim-tabby, although my garbled text is a bit different:

^[[2;2R^[[3;1R^[[>1;115;0c^[110;rgb:ffff/ffff/ffff^G^[]11;rgb:0000/0000/0000^G

ctrl-L clears it.

[gramosg]

Same problem here with Vim 9.1.16 'huge', using the latest vim-plug and vim-tabby. But, one interesting thing I've noted is that it somewhat depends on the terminal emulator:

• In my current setup (Ubuntu 24, Sway, foot terminal) this text appears consistently:

+r436f=323536^[\^[P0+r6b75^[\^[P0+r6b64^[\^[P0+r6b72^[\^[P0+r6b6c^[\^[P0+r2332^[\^[P0+r2334^[\^[P0+r2569^[\^[P0+r2a37^[\^[P0+r6b31^[\

• Switching to kitty makes the text appear very briefly (even before the vim theme has been applied), but then is disappears and vim renders correctly. At the same time kitty shows this error, which may be related because it only happens with vim-tabby enabled:

[219 10:48:22.485623] [PARSE ERROR] The application is trying to use xterm's modifyOtherKeys.
This is superseded by the kitty keyboard protocol: https://sw.kovidgoyal.net/kitty/keyboard-protocol/
the application should be updated to use that

• alacritty does not show any text whatsoever.

@yurivict and @Geremia could you please share what terminal emulators were you using when you had this problem, and whether it was running under Xorg or Wayland? Maybe it helps to pinpoint the cause of this issue :)

[Geremia]

@gramosg

$ echo $SHELL $TERM
/bin/bash xterm-256color

X11 (not Wayland) on Linux (within KDE Konsole terminal app).