Urxvt and tmux - set window title
When I use tmux from urxvt, window title is not updated. Normally when I use just urxvt, window title is updated every time I change directory and it is in form of "$USER@$HOST:$PWD", but when I run tmux from urxvt, window title stays the same as it was before running tmux.
I have tried different set terminal-overrides in tmux.conf as suggested in some answers I found on google, but none worked.
Has anybody managed to make it work? I use Xmonad as WM, but same config works if I run tmux from xterm (title changed accordingly to set-titles-string in tmux.conf), so I guess that tmux and urxvt does not really understand each other.
Versions of software:
rxvt-unicode (urxvt) v9.21 - released: 2014-12-31
tmux 1.9
My dotfiles:
https://github.com/overlordtm/dotfiles
tmux window-manager rxvt
add a comment |
When I use tmux from urxvt, window title is not updated. Normally when I use just urxvt, window title is updated every time I change directory and it is in form of "$USER@$HOST:$PWD", but when I run tmux from urxvt, window title stays the same as it was before running tmux.
I have tried different set terminal-overrides in tmux.conf as suggested in some answers I found on google, but none worked.
Has anybody managed to make it work? I use Xmonad as WM, but same config works if I run tmux from xterm (title changed accordingly to set-titles-string in tmux.conf), so I guess that tmux and urxvt does not really understand each other.
Versions of software:
rxvt-unicode (urxvt) v9.21 - released: 2014-12-31
tmux 1.9
My dotfiles:
https://github.com/overlordtm/dotfiles
tmux window-manager rxvt
add a comment |
When I use tmux from urxvt, window title is not updated. Normally when I use just urxvt, window title is updated every time I change directory and it is in form of "$USER@$HOST:$PWD", but when I run tmux from urxvt, window title stays the same as it was before running tmux.
I have tried different set terminal-overrides in tmux.conf as suggested in some answers I found on google, but none worked.
Has anybody managed to make it work? I use Xmonad as WM, but same config works if I run tmux from xterm (title changed accordingly to set-titles-string in tmux.conf), so I guess that tmux and urxvt does not really understand each other.
Versions of software:
rxvt-unicode (urxvt) v9.21 - released: 2014-12-31
tmux 1.9
My dotfiles:
https://github.com/overlordtm/dotfiles
tmux window-manager rxvt
When I use tmux from urxvt, window title is not updated. Normally when I use just urxvt, window title is updated every time I change directory and it is in form of "$USER@$HOST:$PWD", but when I run tmux from urxvt, window title stays the same as it was before running tmux.
I have tried different set terminal-overrides in tmux.conf as suggested in some answers I found on google, but none worked.
Has anybody managed to make it work? I use Xmonad as WM, but same config works if I run tmux from xterm (title changed accordingly to set-titles-string in tmux.conf), so I guess that tmux and urxvt does not really understand each other.
Versions of software:
rxvt-unicode (urxvt) v9.21 - released: 2014-12-31
tmux 1.9
My dotfiles:
https://github.com/overlordtm/dotfiles
tmux window-manager rxvt
tmux window-manager rxvt
edited Jul 15 '15 at 9:07
asked Jul 15 '15 at 8:56
Andraz
1013
1013
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
tmux
looks at the terminal description to see if it can set the title:
- if the terminal description has the ncurses extended capability
XT
or
- if the terminal description has the terminfo capabilities
fsl
andtsl
(from- and to-status-line).
ncurses' terminfo database has defined XT
for xterm entries for some time (since 2010); there is a discussion of the criteria for that in the ncurses database in Screen Extensions.
Only occasional entries might define the other capabilities for urxvt. If you did not modify the entry, it probably does not include fsl/tsl. The discussion in the terminal database explains why fsl/tsl are not recommended:
# These building-blocks allow access to the X titlebar and icon name as a
# status line. There are a few problems in using them in entries:
#
# a) tsl should have a parameter to denote the column on which to transfer to
# the status line.
# b) the "0" code for xterm updates both icon-title and window title. Some
# window managers such as twm (and possibly window managers descended from
# it such as tvtwm, ctwm, and vtwm) track windows by icon-name. Thus, you
# don't want to mess with icon-name when using those window managers.
#
# The extension "TS" is preferable, because it does not accept a parameter.
# However, if you are using a non-extended terminfo, "TS" is not visible.
xterm+sl|access X title line and icon name,
hs,
dsl=E]0;07, fsl=^G, tsl=E]0;, TS=E]0;,
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f216114%2furxvt-and-tmux-set-window-title%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
tmux
looks at the terminal description to see if it can set the title:
- if the terminal description has the ncurses extended capability
XT
or
- if the terminal description has the terminfo capabilities
fsl
andtsl
(from- and to-status-line).
ncurses' terminfo database has defined XT
for xterm entries for some time (since 2010); there is a discussion of the criteria for that in the ncurses database in Screen Extensions.
Only occasional entries might define the other capabilities for urxvt. If you did not modify the entry, it probably does not include fsl/tsl. The discussion in the terminal database explains why fsl/tsl are not recommended:
# These building-blocks allow access to the X titlebar and icon name as a
# status line. There are a few problems in using them in entries:
#
# a) tsl should have a parameter to denote the column on which to transfer to
# the status line.
# b) the "0" code for xterm updates both icon-title and window title. Some
# window managers such as twm (and possibly window managers descended from
# it such as tvtwm, ctwm, and vtwm) track windows by icon-name. Thus, you
# don't want to mess with icon-name when using those window managers.
#
# The extension "TS" is preferable, because it does not accept a parameter.
# However, if you are using a non-extended terminfo, "TS" is not visible.
xterm+sl|access X title line and icon name,
hs,
dsl=E]0;07, fsl=^G, tsl=E]0;, TS=E]0;,
add a comment |
tmux
looks at the terminal description to see if it can set the title:
- if the terminal description has the ncurses extended capability
XT
or
- if the terminal description has the terminfo capabilities
fsl
andtsl
(from- and to-status-line).
ncurses' terminfo database has defined XT
for xterm entries for some time (since 2010); there is a discussion of the criteria for that in the ncurses database in Screen Extensions.
Only occasional entries might define the other capabilities for urxvt. If you did not modify the entry, it probably does not include fsl/tsl. The discussion in the terminal database explains why fsl/tsl are not recommended:
# These building-blocks allow access to the X titlebar and icon name as a
# status line. There are a few problems in using them in entries:
#
# a) tsl should have a parameter to denote the column on which to transfer to
# the status line.
# b) the "0" code for xterm updates both icon-title and window title. Some
# window managers such as twm (and possibly window managers descended from
# it such as tvtwm, ctwm, and vtwm) track windows by icon-name. Thus, you
# don't want to mess with icon-name when using those window managers.
#
# The extension "TS" is preferable, because it does not accept a parameter.
# However, if you are using a non-extended terminfo, "TS" is not visible.
xterm+sl|access X title line and icon name,
hs,
dsl=E]0;07, fsl=^G, tsl=E]0;, TS=E]0;,
add a comment |
tmux
looks at the terminal description to see if it can set the title:
- if the terminal description has the ncurses extended capability
XT
or
- if the terminal description has the terminfo capabilities
fsl
andtsl
(from- and to-status-line).
ncurses' terminfo database has defined XT
for xterm entries for some time (since 2010); there is a discussion of the criteria for that in the ncurses database in Screen Extensions.
Only occasional entries might define the other capabilities for urxvt. If you did not modify the entry, it probably does not include fsl/tsl. The discussion in the terminal database explains why fsl/tsl are not recommended:
# These building-blocks allow access to the X titlebar and icon name as a
# status line. There are a few problems in using them in entries:
#
# a) tsl should have a parameter to denote the column on which to transfer to
# the status line.
# b) the "0" code for xterm updates both icon-title and window title. Some
# window managers such as twm (and possibly window managers descended from
# it such as tvtwm, ctwm, and vtwm) track windows by icon-name. Thus, you
# don't want to mess with icon-name when using those window managers.
#
# The extension "TS" is preferable, because it does not accept a parameter.
# However, if you are using a non-extended terminfo, "TS" is not visible.
xterm+sl|access X title line and icon name,
hs,
dsl=E]0;07, fsl=^G, tsl=E]0;, TS=E]0;,
tmux
looks at the terminal description to see if it can set the title:
- if the terminal description has the ncurses extended capability
XT
or
- if the terminal description has the terminfo capabilities
fsl
andtsl
(from- and to-status-line).
ncurses' terminfo database has defined XT
for xterm entries for some time (since 2010); there is a discussion of the criteria for that in the ncurses database in Screen Extensions.
Only occasional entries might define the other capabilities for urxvt. If you did not modify the entry, it probably does not include fsl/tsl. The discussion in the terminal database explains why fsl/tsl are not recommended:
# These building-blocks allow access to the X titlebar and icon name as a
# status line. There are a few problems in using them in entries:
#
# a) tsl should have a parameter to denote the column on which to transfer to
# the status line.
# b) the "0" code for xterm updates both icon-title and window title. Some
# window managers such as twm (and possibly window managers descended from
# it such as tvtwm, ctwm, and vtwm) track windows by icon-name. Thus, you
# don't want to mess with icon-name when using those window managers.
#
# The extension "TS" is preferable, because it does not accept a parameter.
# However, if you are using a non-extended terminfo, "TS" is not visible.
xterm+sl|access X title line and icon name,
hs,
dsl=E]0;07, fsl=^G, tsl=E]0;, TS=E]0;,
edited Jun 28 '16 at 22:29
answered Jun 28 '16 at 22:18
Thomas Dickey
52k594164
52k594164
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f216114%2furxvt-and-tmux-set-window-title%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown