Discussion:
terminal-overrides for rxvt-unicode
Daniel Hahler
2014-12-20 05:01:56 UTC
Permalink
Hello,

I've been using urxvt/rxvt-unicode with TERM=xterm-256color for a while,
but now switched back to its default (TERM=rxvt-unicode-256color).

But the defaults for "terminal-overrides" in tmux only consider xterm*:

",xterm*:XT:Ms=\\E]52;%p1%s;%p2%s\\007"
":Cs=\\E]12;%p1%s\\007:Cr=\\E]112\\007"
":Ss=\\E[%p1%d q:Se=\\E[2 q,screen*:XT"

I don't know about "Ms" to modify the selection (probably not supported),
but Cs/Cr (cursor colour) and Ss/Se (cursor style) are supported by
rxvt-unicode in the same way.

Is this worth changing/extending the defaults, or are rxvt-unicode users
supposed to configure it themselves?

Maybe terminal-overrides could allow for multiple patterns to avoid
duplication of options, so that 'xterm*|rxvt*' could be used.

Please note that I don't know if "rxvt*" would be correct here, or if the
more restrictive "rxvt-unicode*" should be used.

Apart from that: the default documented in the man page tmux(1) should
get updated in any way. It currently says it would be
"*256col*:colors=256,xterm*:XT".


Thanks,
Daniel.
--
http://daniel.hahler.de/
Nicholas Marriott
2014-12-20 08:48:25 UTC
Permalink
Hi

I don't want to carry around a huge set of defaults for random
terminals, the xterm one is enough of an example.
Post by Daniel Hahler
Hello,
I've been using urxvt/rxvt-unicode with TERM=xterm-256color for a while,
but now switched back to its default (TERM=rxvt-unicode-256color).
",xterm*:XT:Ms=\\E]52;%p1%s;%p2%s\\007"
":Cs=\\E]12;%p1%s\\007:Cr=\\E]112\\007"
":Ss=\\E[%p1%d q:Se=\\E[2 q,screen*:XT"
I don't know about "Ms" to modify the selection (probably not supported),
but Cs/Cr (cursor colour) and Ss/Se (cursor style) are supported by
rxvt-unicode in the same way.
Is this worth changing/extending the defaults, or are rxvt-unicode users
supposed to configure it themselves?
Maybe terminal-overrides could allow for multiple patterns to avoid
duplication of options, so that 'xterm*|rxvt*' could be used.
Please note that I don't know if "rxvt*" would be correct here, or if the
more restrictive "rxvt-unicode*" should be used.
Apart from that: the default documented in the man page tmux(1) should
get updated in any way. It currently says it would be
"*256col*:colors=256,xterm*:XT".
Thanks,
Daniel.
--
http://daniel.hahler.de/
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
_______________________________________________
tmux-users mailing list
https://lists.sourceforge.net/lists/listinfo/tmux-users
Daniel Hahler
2014-12-20 04:14:40 UTC
Permalink
Hello,

I've been using urxvt/rxvt-unicode with TERM=xterm-256color for a while,
but now switched back to its default (TERM=rxvt-unicode-256color).

But the defaults for "terminal-overrides" in tmux only consider xterm*:

",xterm*:XT:Ms=\\E]52;%p1%s;%p2%s\\007"
":Cs=\\E]12;%p1%s\\007:Cr=\\E]112\\007"
":Ss=\\E[%p1%d q:Se=\\E[2 q,screen*:XT"

I don't know about "Ms" to modify the selection (probably not supported),
but Cs/Cr (cursor colour) and Ss/Se (cursor style) are supported by
rxvt-unicode in the same way.

Is this worth changing/extending the defaults, or are rxvt-unicode users
supposed to configure it themselves?

Maybe terminal-overrides could allow for multiple patterns to avoid
duplication of options, so that 'xterm*|rxvt*' could be used.

Please note that I don't know if "rxvt*" would be correct here, or if the
more restrictive "rxvt-unicode*" should be used.

Apart from that: the default documented in the man page tmux(1) should
get updated in any way. It currently says it would be
"*256col*:colors=256,xterm*:XT".


Thanks,
Daniel.
--
http://daniel.hahler.de/
Loading...