Open dbaldy opened 1 year ago
Thanks for the report, @dbaldy.
I tried to repro this with iTerm (Build 3.4.21), with kitty (Version 0.30.1), and inside and outside of tmux (tmux next-3.4, built from source) but it doesn't repro for me.
At first I thought it might be due to the new allow-passthrough
setting that defaults to off
, and which was added not that long ago to tmux, but I don't see any difference in behavior with this line present or commented out in my ~/.config/tmux/tmux.conf
:
set-option -g allow-passthrough all
So, I think for now we just leave this issue open with your workaround for others to find and comment on, and if we get a clearer picture of the exact conditions under which this repros then we can try to find a general fix for it.
I am on MacOS with iTerm2 version 3.4.19.
What I get when I type set
with the uncommented code:
With the commented code (working version):
My tmux.conf
looks as follows:
set-window-option -g mode-keys vi
set -g default-terminal "xterm-256color"
After quite some tinkering, it turns out that terminus doesn't change the cursor shape in my iTerm2 with Tmux.
I found that the right setup was using the standard terminal option and commenting out the tmux specific update:
I'm running
TERM_PROGRAM_VERSION=3.3a
I don't know why that could be the case, I'm not super knowledgeable about that but if someone has the same issue at least they can find a workaround.
For anyone else having the same issue: the lines to comment out are in <vim plugin directory>/terminus/plugin/terminus.vim
, lines 46 - 54, 62 - 68.
This is occurring for me with:
Cursor shape for me wasn't changing as well. Following the advice from OP worked.
Im running:
Same problem and solution on ubuntu with kitty terminal for me:
After quite some tinkering, it turns out that terminus doesn't change the cursor shape in my iTerm2 with Tmux.
I found that the right setup was using the standard terminal option and commenting out the tmux specific update:
I'm running
TERM_PROGRAM_VERSION=3.3a
I don't know why that could be the case, I'm not super knowledgeable about that but if someone has the same issue at least they can find a workaround.