I can reproduce this issue with tmux-3.1b, tmux-3.1 e94bd5c (2020.11.10's master), and vim 8.2.1805, vim 8.2.1943, vim 8.2.2000.
The terminal is urxvt maximized.
With this plugin loaded the tmux server always crashed with a fatal error message, as explained below.
When this plugin wasn't loaded the tmux server never crashed.
"Crashed" means that the server catches an invalid event, emits a fatal error message and exits with status 1.
Start the very first tmux client running my shell (zsh) -- tmux server wasn't running yet.
Maximize the terminal, run vim somefile, press o to insert a new line and leave it there.
Switch to another window -- in my case it's always a maximized chromium if that matters.
At this point urxvt disappears from the screen with vim inside it. Looking at the tmux server's log (enabled with SIGUSR2) I can see that the tmux server has closed with status 1 and a "fatal" error message, "invalid key modifier". See the attached log file. The log's tail reads:
Stop the press! The server just crashed when this plugin wasn't loaded, and logged the same error message. I'm closing this issue right away as it doesn't pertain to this plugin. Sorry for any inconvenience.
Thank you for your plugins.
I can reproduce this issue with tmux-3.1b, tmux-3.1 e94bd5c (2020.11.10's master), and vim 8.2.1805, vim 8.2.1943, vim 8.2.2000. The terminal is urxvt maximized.
With this plugin loaded the tmux server always crashed with a fatal error message, as explained below. When this plugin wasn't loaded the tmux server never crashed. "Crashed" means that the server catches an invalid event, emits a fatal error message and exits with status 1.
vim somefile
, presso
to insert a new line and leave it there.At this point urxvt disappears from the screen with vim inside it. Looking at the tmux server's log (enabled with SIGUSR2) I can see that the tmux server has closed with status 1 and a "fatal" error message, "invalid key modifier". See the attached log file. The log's tail reads:
tmux-server-23005.log.tar.gz