Extending GNU Screen - Adding a taskbar
Posted in Howto, Tipps on January 17th, 2009 by Benjamin Milde – 3 CommentsOne of the biggest drawbacks of GNU Screen is that you don’t see an overview of your virtual terminals in most standard configurations. But that can be easily changed. My screen now looks like this:
Screenshot of extented screen with taskbar
You can clearly see which programs are running and you have a good overview. The other goodies like cpu load display and the clock is also very practical.
The global configuration file /etc/screenrc already has some minor tweaks (Depending on your distribution). If you only want the taskbar for a particular user, than the local .screenrc in your home directory is the file to edit.
The heart of my screen configuration is:
backtick 1 0 0 /usr/bin/cpuusage
hardstatus alwayslastline
hardstatus string '%{= kG} %{G}%H %{g}[%= %{=kw}%?%-Lw%?%{r}(%{W}%n*%f%t%?(%u)%?%{r})%{w}%?%+Lw%?%?%= %{g}] %1`%% CPU %{W}%c %{g}’
With “backtick” a command-directive (1 here - must be a number) is noted. The “0 0″ then means that whenever a new output from the program is produced, screen stores the last line of output. “Hardstatus” is for the taskbar and each % directive is for special purposes. With `% 1 for example the last line of the backtick command is printed. For all the other directives better read the GNU screen-manpage
The cpuusage-script looks like this:
#!/bin/bashawk ‘BEGIN {file = "/proc/stat";while (a==a) {getline < file;u=$2-up;s=$3-sp;n=$4-np;i=$5-ip;printf ("%2.1f\n"),(u+s)/(u+s+n+i)*100;up=$2;sp=$3;np=$4;ip=$5;close(file);system("sleep 1")}}’- Download this code: cpuusage
This awk-oneliner uses the information from /proc/stat to calculate the cpuload for one second. That is supported on all unixes with proc support (Mac OS X has no proc).
What’s missing now, is dynamic window titles. In the previous configuration, all titles are set to “n * bash”, we had to change the titles manually.
With a special escape-sequence, the title can be set from the console. The screen manpage explains the procedure:
The default name for all shell windows can be set with the "shelltitle"
command in the .screenrc file, while all other windows are created with
a "screen" command and thus can have their name set with the -t option.
Interactively, there is the title-string escape-sequence
(
output from an application to control the window’s name under software
control, and the latter will prompt for a name when typed. You can
also bind pre-defined names to keys with the “title” command to set
things quickly without prompting.
Finally, screen has a shell-specific heuristic that is enabled by set-
ting the window’s name to “search|name” and arranging to have a null
title escape-sequence output as a part of your prompt. The search por-
tion specifies an end-of-prompt search string, while the name portion
specifies the default shell name for the window. If the name ends in a
‘:’ screen will add what it believes to be the current command running
in the window to the end of the window’s shell name (e.g. “name:cmd”).
Otherwise the current command name supersedes the shell name while it
is running.
Here’s how it works: you must modify your shell prompt to output a
null title-escape-sequence (
The last part of your prompt must be the same as the string you speci-
fied for the search portion of the title. Once this is set up, screen
will use the title-escape-sequence to clear the previous command name
and get ready for the next command. Then, when a newline is received
from the shell, a search is made for the end of the prompt. If found,
it will grab the first word after the matched string and use it as the
command name. If the command name begins with either ‘!’, ‘%’, or ‘^’
screen will use the first word on the following line (if found) in
preference to the just-found name. This helps csh users get better
command names when using job control or history recall commands.
My shellprompt looks like this:
server1 pastacode #
That means, all my commands are typed in after the #. So, I have to add this to my .shellrc :
#dynamic title
shelltitle '# |bash'
Screen now looks for a # when it gets the escape-sequence. “| Bash” means that the default title is “Bash”. We now only need the escape sequence in our promt; that can be customized (in Bash) with the PS1 variable. To do this we will either edit the /etc/bashrc (for any user) or the local .bashrc in our home directory. My .bashrc looks like this:
export EDITOR=/usr/bin/vi# Set the screen titlecase $TERM inscreen*)# This is the escape sequence ESC k \w ESC \#Use path as titel#SCREENTITLE=’\[\ek\w\e\\\]‘#Use program name as titelSCREENTITLE=‘\[\ek\e\\\]‘;;*)SCREENTITLE=”;;esacPS1="${SCREENTITLE}${PS1}"- Download this code: bashrc
The PS1 is altered to add the screen escape-sequence, but only when we are in screen. In my file, you can actually choose between two versions: either the current path is the dynamic title, or the program name, although I prefer the latter. Unfortunately viewing both seems to be not a trivial thing.
So I hope the whole thing works for you - for suggestions, better ideas - write a comment!
Last but not least my complete .screenrc:
#no bells and startup messagesstartup_message offvbell off#10000 lines scrollback bufferdefscrollback 10000#no logindeflogin off# Default shellshell bash#Timeout for displaying messagesmsgwait 1activity " Activity has appeared in window %n - %t"#taskbarbacktick 1 0 0 /usr/bin/cpuusagehardstatus alwayslastlinehardstatus string ‘%{= kG} %{G}%H %{g}[%= %{=kw}%?%-Lw%?%{r}(%{W}%n*%f%t%?(%u)%?%{r})%{w}%?%+Lw%?%?%= %{g}] %1`%% CPU %{W}%c %{g}’#dynamic titleshelltitle ‘# |bash’#When your ssh connection dies, screen is autodetachedautodetach on#Nice 256 term colorsattrcolor b ".I"termcapinfo xterm ‘Co#256:AB=\E[48;5;%dm:AF=\E[38;5;%dm’- Download this code: screenrc
And the cpuusage script:
#!/bin/bashawk ‘BEGIN {file = "/proc/stat";while (a==a) {getline < file;u=$2-up;s=$3-sp;n=$4-np;i=$5-ip;printf ("%2.1f\n"),(u+s)/(u+s+n+i)*100;up=$2;sp=$3;np=$4;ip=$5;close(file);system("sleep 1")}}’- Download this code: cpuusage
Sources:
The pages below helped me alot:
http://listserv.ccjclearline.com/pipermail/kwlug-disc/2006-November/002132.html
http://b79.net/code/screenrc
http://www.mediacollege.com/cgi-bin/man/page.cgi?topic=screen
