-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cursor change not working in iTerm2 with tmux 3.3a #53
Comments
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
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. |
For anyone else having the same issue: the lines to comment out are in 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:
|
at least under Ventura + iterm2 + tmux 3.4 Per wincent/terminus#53
at least under Ventura + iterm2 + tmux 3.4 Per wincent/terminus#53
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:
![image](https://private-user-images.githubusercontent.com/16085513/275717749-8f430b80-e1b9-4e09-8bfa-051570818e50.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkxMjk0MTAsIm5iZiI6MTczOTEyOTExMCwicGF0aCI6Ii8xNjA4NTUxMy8yNzU3MTc3NDktOGY0MzBiODAtZTFiOS00ZTA5LThiZmEtMDUxNTcwODE4ZTUwLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMDklMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjA5VDE5MjUxMFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTEzZmVlODRlOWQxYWNlMzI3NjI3N2UxZDBjNmI1ZWM1NDhjOGZmODczZGU5ZGNhMzRkMDg1OGU1MWJhZmI1ZDkmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.6GXMKsVdypZR70SFX4eMLhbgoInO0ieJmT3UejQjiN4)
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.
The text was updated successfully, but these errors were encountered: