Screen status bar multiple lines
I am using screen with several tabs open to separate my projects between them. However, when I open too many tabs they just appear off screen and I can no longer see them in my "screen status bar". I can still switch to them, but not see them in my list of windows. How can I make it so that my "screen status bar" will expand to two lines when necessary? I've gotten a .screenrc from a friend to start with which put me where I'm at, but I'd like to customize it to afford me this option.
gnu-screen
edited Mar 30 '11 at 16:10
Michael Mrozek♦
60.6k29187208
asked Mar 30 '11 at 15:56
Diego
224139
add a comment |
I am using screen with several tabs open to separate my projects between them. However, when I open too many tabs they just appear off screen and I can no longer see them in my "screen status bar". I can still switch to them, but not see them in my list of windows. How can I make it so that my "screen status bar" will expand to two lines when necessary? I've gotten a .screenrc from a friend to start with which put me where I'm at, but I'd like to customize it to afford me this option.
gnu-screen
edited Mar 30 '11 at 16:10
Michael Mrozek♦
60.6k29187208
asked Mar 30 '11 at 15:56
Diego
224139
add a comment |
I am using screen with several tabs open to separate my projects between them. However, when I open too many tabs they just appear off screen and I can no longer see them in my "screen status bar". I can still switch to them, but not see them in my list of windows. How can I make it so that my "screen status bar" will expand to two lines when necessary? I've gotten a .screenrc from a friend to start with which put me where I'm at, but I'd like to customize it to afford me this option.
gnu-screen
edited Mar 30 '11 at 16:10
Michael Mrozek♦
60.6k29187208
asked Mar 30 '11 at 15:56
Diego
224139
I am using screen with several tabs open to separate my projects between them. However, when I open too many tabs they just appear off screen and I can no longer see them in my "screen status bar". I can still switch to them, but not see them in my list of windows. How can I make it so that my "screen status bar" will expand to two lines when necessary? I've gotten a .screenrc from a friend to start with which put me where I'm at, but I'd like to customize it to afford me this option.
gnu-screen
gnu-screen
edited Mar 30 '11 at 16:10
Michael Mrozek♦
60.6k29187208
asked Mar 30 '11 at 15:56
Diego
224139
edited Mar 30 '11 at 16:10
Michael Mrozek♦
60.6k29187208
asked Mar 30 '11 at 15:56
Diego
224139
edited Mar 30 '11 at 16:10
Michael Mrozek♦
60.6k29187208
edited Mar 30 '11 at 16:10
Michael Mrozek♦
60.6k29187208
edited Mar 30 '11 at 16:10
Michael Mrozek♦
60.6k29187208
60.6k29187208
asked Mar 30 '11 at 15:56
Diego
224139
asked Mar 30 '11 at 15:56
Diego
224139
asked Mar 30 '11 at 15:56
Diego
224139
224139
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
I turn off the status bar, myself, because that's not a pratical way to manage screen with 40+ windows. Using Ctrl-A + " will open a list of all screens. You can name individual windows with Ctrl-A + A. I also use a customized .screenrc that, among other things, shows the Shell Title message in the Window listing.
# terminfo and termcap for nice 256 color terminal
# allow bold colors - necessary for some reason
attrcolor b ".I"
# tell screen how to set colors. AB = background, AF=foreground
#termcapinfo xterm 'ti=E[?1049h:te=E[?1049l'
#termcapinfo xterm 'Co#256:AB=E[48;5;%dm:AF=E[38;5;%dm:hs:ts=E]2;:fs=07:ds=E]2;screen07'
termcapinfo xterm* 'Co#256:AB=E[48;5;%dm:AF=E[38;5;%dm:hs:ts=E]2;:fs=07:ds=E]2;screen07:ti=E[?1049h:te=E[?1049l:XT'
termcapinfo screen* 'Co#256:AB=E[48;5;%dm:AF=E[38;5;%dm:hs:ts=E]2;:fs=E\:ds=E]2;screenE\:ti=E[?1049h:te=E[?1049l:XT'
# erase background with current bg color
defbce "on"
altscreen on
#hardstatus on
defscrollback 2000
multiuser on
hardstatus string "[%n%?: %t%?] %h"
windowlist string "%3n %t %h%=%f"
answered Mar 31 '11 at 5:14
penguin359
8,70423040
Personally I'd rather stick with the key mappings and setup I already have. I wont need to manage 40 or more screens just about 15 so I would one more row to make it perfect!! Thanks though
– Diego
Mar 31 '11 at 11:50
I am using screen's default keymappings. The only line I'd recommend above is windowlist. It will make the window list much more useful. The rest of that file does things like enable 256 color mode and enable XTerm titles.
– penguin359
Mar 31 '11 at 12:33
add a comment |
I have a hint about how to make it work: screen in a screen.
Draft of such a solution workaround:
- Your original screen with:
- a backtick function that writes (into a file) the information needed to be shown in the second line
- New outer screen with:
- a backtick function able to read the inner screen's information (the file)
- a custom config file
- a different prefix (that is never used in the inner screen)
optionally for better user experience:
- run the inner screen in first window
- single window
- will exit when inner ends
answered 7 mins ago
user330003
1
New contributor
user330003 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
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%2f10318%2fscreen-status-bar-multiple-lines%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
I turn off the status bar, myself, because that's not a pratical way to manage screen with 40+ windows. Using Ctrl-A + " will open a list of all screens. You can name individual windows with Ctrl-A + A. I also use a customized .screenrc that, among other things, shows the Shell Title message in the Window listing.
# terminfo and termcap for nice 256 color terminal
# allow bold colors - necessary for some reason
attrcolor b ".I"
# tell screen how to set colors. AB = background, AF=foreground
#termcapinfo xterm 'ti=E[?1049h:te=E[?1049l'
#termcapinfo xterm 'Co#256:AB=E[48;5;%dm:AF=E[38;5;%dm:hs:ts=E]2;:fs=07:ds=E]2;screen07'
termcapinfo xterm* 'Co#256:AB=E[48;5;%dm:AF=E[38;5;%dm:hs:ts=E]2;:fs=07:ds=E]2;screen07:ti=E[?1049h:te=E[?1049l:XT'
termcapinfo screen* 'Co#256:AB=E[48;5;%dm:AF=E[38;5;%dm:hs:ts=E]2;:fs=E\:ds=E]2;screenE\:ti=E[?1049h:te=E[?1049l:XT'
# erase background with current bg color
defbce "on"
altscreen on
#hardstatus on
defscrollback 2000
multiuser on
hardstatus string "[%n%?: %t%?] %h"
windowlist string "%3n %t %h%=%f"
answered Mar 31 '11 at 5:14
penguin359
8,70423040
Personally I'd rather stick with the key mappings and setup I already have. I wont need to manage 40 or more screens just about 15 so I would one more row to make it perfect!! Thanks though
– Diego
Mar 31 '11 at 11:50
I am using screen's default keymappings. The only line I'd recommend above is windowlist. It will make the window list much more useful. The rest of that file does things like enable 256 color mode and enable XTerm titles.
– penguin359
Mar 31 '11 at 12:33
add a comment |
I turn off the status bar, myself, because that's not a pratical way to manage screen with 40+ windows. Using Ctrl-A + " will open a list of all screens. You can name individual windows with Ctrl-A + A. I also use a customized .screenrc that, among other things, shows the Shell Title message in the Window listing.
# terminfo and termcap for nice 256 color terminal
# allow bold colors - necessary for some reason
attrcolor b ".I"
# tell screen how to set colors. AB = background, AF=foreground
#termcapinfo xterm 'ti=E[?1049h:te=E[?1049l'
#termcapinfo xterm 'Co#256:AB=E[48;5;%dm:AF=E[38;5;%dm:hs:ts=E]2;:fs=07:ds=E]2;screen07'
termcapinfo xterm* 'Co#256:AB=E[48;5;%dm:AF=E[38;5;%dm:hs:ts=E]2;:fs=07:ds=E]2;screen07:ti=E[?1049h:te=E[?1049l:XT'
termcapinfo screen* 'Co#256:AB=E[48;5;%dm:AF=E[38;5;%dm:hs:ts=E]2;:fs=E\:ds=E]2;screenE\:ti=E[?1049h:te=E[?1049l:XT'
# erase background with current bg color
defbce "on"
altscreen on
#hardstatus on
defscrollback 2000
multiuser on
hardstatus string "[%n%?: %t%?] %h"
windowlist string "%3n %t %h%=%f"
answered Mar 31 '11 at 5:14
penguin359
8,70423040
Personally I'd rather stick with the key mappings and setup I already have. I wont need to manage 40 or more screens just about 15 so I would one more row to make it perfect!! Thanks though
– Diego
Mar 31 '11 at 11:50
I am using screen's default keymappings. The only line I'd recommend above is windowlist. It will make the window list much more useful. The rest of that file does things like enable 256 color mode and enable XTerm titles.
– penguin359
Mar 31 '11 at 12:33
add a comment |
I turn off the status bar, myself, because that's not a pratical way to manage screen with 40+ windows. Using Ctrl-A + " will open a list of all screens. You can name individual windows with Ctrl-A + A. I also use a customized .screenrc that, among other things, shows the Shell Title message in the Window listing.
# terminfo and termcap for nice 256 color terminal
# allow bold colors - necessary for some reason
attrcolor b ".I"
# tell screen how to set colors. AB = background, AF=foreground
#termcapinfo xterm 'ti=E[?1049h:te=E[?1049l'
#termcapinfo xterm 'Co#256:AB=E[48;5;%dm:AF=E[38;5;%dm:hs:ts=E]2;:fs=07:ds=E]2;screen07'
termcapinfo xterm* 'Co#256:AB=E[48;5;%dm:AF=E[38;5;%dm:hs:ts=E]2;:fs=07:ds=E]2;screen07:ti=E[?1049h:te=E[?1049l:XT'
termcapinfo screen* 'Co#256:AB=E[48;5;%dm:AF=E[38;5;%dm:hs:ts=E]2;:fs=E\:ds=E]2;screenE\:ti=E[?1049h:te=E[?1049l:XT'
# erase background with current bg color
defbce "on"
altscreen on
#hardstatus on
defscrollback 2000
multiuser on
hardstatus string "[%n%?: %t%?] %h"
windowlist string "%3n %t %h%=%f"
answered Mar 31 '11 at 5:14
penguin359
8,70423040
I turn off the status bar, myself, because that's not a pratical way to manage screen with 40+ windows. Using Ctrl-A + " will open a list of all screens. You can name individual windows with Ctrl-A + A. I also use a customized .screenrc that, among other things, shows the Shell Title message in the Window listing.
# terminfo and termcap for nice 256 color terminal
# allow bold colors - necessary for some reason
attrcolor b ".I"
# tell screen how to set colors. AB = background, AF=foreground
#termcapinfo xterm 'ti=E[?1049h:te=E[?1049l'
#termcapinfo xterm 'Co#256:AB=E[48;5;%dm:AF=E[38;5;%dm:hs:ts=E]2;:fs=07:ds=E]2;screen07'
termcapinfo xterm* 'Co#256:AB=E[48;5;%dm:AF=E[38;5;%dm:hs:ts=E]2;:fs=07:ds=E]2;screen07:ti=E[?1049h:te=E[?1049l:XT'
termcapinfo screen* 'Co#256:AB=E[48;5;%dm:AF=E[38;5;%dm:hs:ts=E]2;:fs=E\:ds=E]2;screenE\:ti=E[?1049h:te=E[?1049l:XT'
# erase background with current bg color
defbce "on"
altscreen on
#hardstatus on
defscrollback 2000
multiuser on
hardstatus string "[%n%?: %t%?] %h"
windowlist string "%3n %t %h%=%f"
answered Mar 31 '11 at 5:14
penguin359
8,70423040
answered Mar 31 '11 at 5:14
penguin359
8,70423040
answered Mar 31 '11 at 5:14
penguin359
8,70423040
answered Mar 31 '11 at 5:14
penguin359
8,70423040
8,70423040
Personally I'd rather stick with the key mappings and setup I already have. I wont need to manage 40 or more screens just about 15 so I would one more row to make it perfect!! Thanks though
– Diego
Mar 31 '11 at 11:50
I am using screen's default keymappings. The only line I'd recommend above is windowlist. It will make the window list much more useful. The rest of that file does things like enable 256 color mode and enable XTerm titles.
– penguin359
Mar 31 '11 at 12:33
add a comment |
Personally I'd rather stick with the key mappings and setup I already have. I wont need to manage 40 or more screens just about 15 so I would one more row to make it perfect!! Thanks though
– Diego
Mar 31 '11 at 11:50
I am using screen's default keymappings. The only line I'd recommend above is windowlist. It will make the window list much more useful. The rest of that file does things like enable 256 color mode and enable XTerm titles.
– penguin359
Mar 31 '11 at 12:33
Personally I'd rather stick with the key mappings and setup I already have. I wont need to manage 40 or more screens just about 15 so I would one more row to make it perfect!! Thanks though
– Diego
Mar 31 '11 at 11:50
Personally I'd rather stick with the key mappings and setup I already have. I wont need to manage 40 or more screens just about 15 so I would one more row to make it perfect!! Thanks though
– Diego
Mar 31 '11 at 11:50
I am using screen's default keymappings. The only line I'd recommend above is windowlist. It will make the window list much more useful. The rest of that file does things like enable 256 color mode and enable XTerm titles.
– penguin359
Mar 31 '11 at 12:33
I am using screen's default keymappings. The only line I'd recommend above is windowlist. It will make the window list much more useful. The rest of that file does things like enable 256 color mode and enable XTerm titles.
– penguin359
Mar 31 '11 at 12:33
add a comment |
I have a hint about how to make it work: screen in a screen.
Draft of such a solution workaround:
- Your original screen with:
- a backtick function that writes (into a file) the information needed to be shown in the second line
- New outer screen with:
- a backtick function able to read the inner screen's information (the file)
- a custom config file
- a different prefix (that is never used in the inner screen)
optionally for better user experience:
- run the inner screen in first window
- single window
- will exit when inner ends
answered 7 mins ago
user330003
1
New contributor
user330003 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I have a hint about how to make it work: screen in a screen.
Draft of such a solution workaround:
- Your original screen with:
- a backtick function that writes (into a file) the information needed to be shown in the second line
- New outer screen with:
- a backtick function able to read the inner screen's information (the file)
- a custom config file
- a different prefix (that is never used in the inner screen)
optionally for better user experience:
- run the inner screen in first window
- single window
- will exit when inner ends
answered 7 mins ago
user330003
1
New contributor
user330003 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I have a hint about how to make it work: screen in a screen.
Draft of such a solution workaround:
- Your original screen with:
- a backtick function that writes (into a file) the information needed to be shown in the second line
- New outer screen with:
- a backtick function able to read the inner screen's information (the file)
- a custom config file
- a different prefix (that is never used in the inner screen)
optionally for better user experience:
- run the inner screen in first window
- single window
- will exit when inner ends
answered 7 mins ago
user330003
1
New contributor
user330003 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I have a hint about how to make it work: screen in a screen.
Draft of such a solution workaround:
- Your original screen with:
- a backtick function that writes (into a file) the information needed to be shown in the second line
- New outer screen with:
- a backtick function able to read the inner screen's information (the file)
- a custom config file
- a different prefix (that is never used in the inner screen)
optionally for better user experience:
- run the inner screen in first window
- single window
- will exit when inner ends
answered 7 mins ago
user330003
1
New contributor
user330003 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 7 mins ago
user330003
1
New contributor
user330003 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 7 mins ago
user330003
1
answered 7 mins ago
user330003
1
1
New contributor
user330003 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
user330003 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
user330003 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
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%2f10318%2fscreen-status-bar-multiple-lines%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
