Skip to content
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

setting xterm escape sequence causes char+112 on prompt #266

Closed
atomi opened this issue Jan 14, 2016 · 4 comments
Closed

setting xterm escape sequence causes char+112 on prompt #266

atomi opened this issue Jan 14, 2016 · 4 comments

Comments

@atomi
Copy link

atomi commented Jan 14, 2016

Using tmux 2.0
If I type echo -ne "\e]12;orange1\a" I get a char+112 on my prompt randomly appearing
screenshot 2016-01-13 15 30 31

I believe it's related to this issue https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1435905

However I already have libvte-2.90-9, yet this issue still occurs but only in tmux. I've tried this on gnome-terminal and roxterm and both do this only under tmux. xterm terminal however seems to work as intended both with or without tmux.

@nicm
Copy link
Member

nicm commented Jan 14, 2016

Default Cr (colour reset) is \033]112\007, probably gnome-terminal does not support this so either you will need to set Cr to something it does support (you can use terminal-overrides) or turn off the cursor colour escape sequences (either in terminal-overrides or with the right TERM).

@atomi
Copy link
Author

atomi commented Jan 14, 2016

Setting Cr

set-option -g terminal-overrides ',xterm*:Cr=\E]12;gray\007'

This solution works for me.
Thank you!

@nicm
Copy link
Member

nicm commented Jan 14, 2016

Ok, great. You probably want set -ag if you have a leading comma.

@nicm nicm closed this as completed Jan 14, 2016
cmcginty added a commit to cmcginty/dotfiles that referenced this issue Jan 27, 2016
@lock
Copy link

lock bot commented Feb 16, 2020

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Feb 16, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

No branches or pull requests

2 participants