GNU Screen Survival Guide

Question

What do people think are not only the essential things you need to know about the excellent Screen utility but the things that you'd think worthwhile to teach someone, a beginner, from the ground up.

I've just introduced a friend to Screen and they're having a hard time getting used to it. So analogies and handy tips for remembering binds etc would be awesome.

Thanks

Answer 1

If your friend is in the habit of pressing ^A to get to the beginning of the line in bash, he/she is in for some surprises, since ^A is the screen command key binding. Usually I end up with a frozen screen, possibly because of some random key I pressed after ^A :-)

In those cases I try

^A s and ^A q block/unblock terminal scrolling

to fix that. To go to the beginning of a line inside screen the key sequence is ^A a

Answer 2

ctrl+a is a special key.

ctrl+a d - [d]etach, leave programs (irssi?) in background, go home.

ctrl+a c [c]reate a new window ctrl+a [0-9] switch between windows by number

screen -r - get back to detached session

That covers 90% of use cases. Do not try to show all the functionality at the single time.

Answer 3

Ctrl+A is the base command

Ctrl+A N = go to the Next screen

Ctrl+A P = go to the Previous screen

Ctrl+A C = Create new screen

Ctrl+A D = Detach your screen

Answer 4

I've been using screen for over 10 years and probably use less than half the features. So it's definitely not necessary to learn all its features right away (and I wouldn't recommend trying). My day-to-day commands are:

^A ^W - window list, where am I
^A ^C - create new window
^A space - next window
^A p - previous window
^A ^A - switch to previous screen (toggle)
^A [0-9] - go to window [0-9]
^A esc - copy mode, which I use for scrollback

I think that's it. I sometimes use the split screen features, but certainly not daily. The other tip is if screen seems to have locked up because you hit some random key combination by accident, do both ^Q and ^A ^Q to try to unlock it.

Answer 5

Ctrl+A ? - show the help screen!

Answer 6

I wrote this guide at my last job. The first section is a must-know crash course, and subsequent sections are more in-depth looks at some major features of the program. For everything else, there's the manpage :)

Answer 7

I couldn't get used to screen until I found a way to set a 'status bar' at the bottom of the screen that shows what 'tab' or 'virtual screen' you're on and which other ones there are. Here is my setup:

[roel@roel ~]$ cat .screenrc
# Here comes the pain...
caption always "%{=b dw}:%{-b dw}:%{=b dk}[ %{-b dw}%{-b dg}$USER%{-b dw}@%{-b dg}%H %{=b dk}] [ %= %?%{-b dg}%-Lw%?%{+b dk}(%{+b dw}%n:%t%{+b dk})%?(%u)%?%{-b dw}%?%{-b dg}%+Lw%? %{=b dk}]%{-b dw}:%{+b dw}:"

backtick 2 5 5 $HOME/scripts/meminfo
hardstatus alwayslastline "%{+b dw}:%{-b dw}:%{+b dk}[%{-b dg} %0C:%s%a %{=b dk}]-[   %{-b dw}Load%{+b dk}:%{-b dg}%l %{+b dk}] [%{-b dg}%2`%{+b dk}] %=[ %{-b dg}%1`%{=b dk} ]%{-b dw}:%{+b dw}:%<"

sorendition "-b dw"
[roel@roel ~]$ cat ~/scripts/meminfo
#!/bin/sh
RAM=`cat /proc/meminfo | grep "MemFree" | awk -F" " '{print $2}'`
SWAP=`cat /proc/meminfo | grep "SwapFree" | awk -F" " '{print $2}'`
echo -n "${RAM}kb/ram ${SWAP}kb/swap"
[roel@roel ~]$

Answer 8

You can remap the escape key from ctrl-A to be another key of your choice, so if you do use it for something else, e.g. to go to the beginning of the line in bash, you just need to add a line to your ~/.screenrc file. To make it ^b or ^B use:

escape ^bB

From the command line, use names sessions to keep multiple sessions under control. I use one session per task, each with multiple tabs:

  screen -ls                lists your current screen sessions
  screen -S <name>          creates a new screen session called name
  screen -r <name>          connects to the named screen sessions

When using screen you only need a few commands:

  ^A c          create a new shell
  ^A [0-9]      switch shell
  ^A k          kill the current shell
  ^A d          disconnect from screen
  ^A ?          show the help

An excellent quick reference can be found here. Worth bookmarking.

Answer 9

^A A switches back to the screen you just came from.

Answer 10

Not really essential not solely related to screen, but enabling 256 colors in my terminal, GNU Screen and Vim improved my screen experience big time (especially since I code in Vim about 8h a day - there are some great eye-friendly colorschemes).

Answer 11

I like to set up a screen session with descriptive names for the windows. ^a A will let you give a name to the current window and ^a " will give you a list of your windows. When done, detach the screen with ^a d and re-attach with screen -R

Answer 12

http://www.debian-administration.org/articles/34

I wrote that a couple of years ago, but it is still a good introduction that gets a lot of positive feedback.

Answer 13

This is for a local screen session. My target - i wnt to back up a detached screens session, or during running a session collect the data needed which i can use o get the same sassion - with the same settings and so on, up and running again.

I need to know about how screen saves its data during sessions. if i look in /var/run/screen/S-username then i have my sesions there - and they are of size null.

Plese can anyone give me some more info about what a screen-session eg is.

And if possible, i prefere to get the ansver in technical terms and not be told that i should 'imagine a pipe of paper" and so on. regards /PeterH

Answer 14

I "must" add this: add

bind s

to your .screenrc, if You - like me - used to use split windows, as C-a S splits the actual window, but C-a s freezes it. So I just disabled the freeze shortcut.

Answer 15

There is some interesting work being done on getting a good gnu-screen setup happening by default in the next version of Ubuntu Server, which includes using the bottom of the screen to show all the windows as well as other useful machine details (like # updates available and whether the machine needs a reboot). You can probably grab their .screenrc and customise it to your needs.

The most useful commands I have in my .screenrc are the following

shelltitle "$ |bash" # make screen assign window titles automatically
hardstatus alwayslastline "%w" # show all window titles at bottom line of term

This way I always know what windows are open, and what is running in them at the moment, too.

Answer 16

The first modification I make to .screenrc is to change the escape command. Not unlike many of you, I do not like the default Ctrl-A sequence because of its interference with that fundamental functionality in almost every other context. In my .screenrc file, I add:

escape `e

That's backtick-e.

This enables me to use the backtick as the escape key (e.g. to create a new screen, I press backtick-c, detach is backtick-d, backtick-? is help, backtick-backtick is previous screen, etc.). The only way it interferes (and I had to break myself of the habit) is using backtick on the command line to capture execution output, or pasting anything that contains a backtick. For the former, I've modified my habit by using the BASH $(command) convention. For the latter, I usually just pop open another xterm or detach from screen then paste the content containing the backtick. Finally, if I wish to insert a literal backtick, I simply press backtick-e.

Answer 17

Some tips for those sorta familiar with screen, but who tend to not remember things they read in the man page:

• To change the name of a screen window is very east: ctrl+A shift+A.
• Did you miss the last message from screen? ctrl+a ctrl+m will show it again for you.
• If you want to run something (like tailing a file) and have screen tell you when there's a change, use ctrl+A shift+m on the target window. Warning: it will let you know if anything changes.
• Want to select window 15 directly? Try these in your .screenrc file:

bind  ! select 11
bind  @ select 12
bind \# select 13
bind  $ select 14
bind  % select 15
bind \^ select 16
bind  & select 17
bind  * select 18
bind  ( select 19
bind  ) select 10

That assigns ctrl+a shift+(0 through 9) for windows 10 through 19.

Answer 18

I can't remember who I stole this from (someone on dotfile.org). I've modified it slightly for ssh:

#!/bin/sh
# scr - Runs a command in a fresh screen
#
# Get the current directory and the name of command

wd=`pwd`
cmd=$1
shift

# We can tell if we are running inside screen by looking
# for the STY environment variable.  If it is not set we
# only need to run the command, but if it is set then
# we need to use screen.

if [ -z "$STY" ]; then
        $cmd $*
else
        # Screen needs to change directory so that
        # relative file names are resolved correctly.
        screen -X chdir $wd

        # Ask screen to run the command
        if [ $cmd == "ssh" ]; then
                screen -X screen -t ""${1##*@}"" $cmd $*
        else
                screen -X screen -t "$cmd $*" $cmd $*
        fi
fi

Then I set the following bash aliases:

vim() {
        scr vim $*
}

man() {
        scr man $*
}

info() {
        scr info $*
}

watch() {
        scr watch $*
}

ssh() {
        scr ssh $*
}

It opens a new screen for the above aliases and iff using ssh, it renames the screen title with the ssh hostname.

Cheers z0mbix

Answer 19

Someone has posted a similar question to this on Server Fault.