Indeed, it is really basic. I guess I could see value in aliasing that to save typing. In my case, I have a "Screen" menu in fvwm with menu entries like this:

Indeed, it is really basic. I guess I could see value in aliasing that to save typing. In my case, I have a "Screen" menu in fvwm with menu entries like this: + %terminal.png%"caspian" Exec exec xterm -geometry 80x25+30-28 -T "screen : caspian" -e ssh -t eki@caspian.vying.org screen -x -R I have menus for local screens as well, with entries like: + %terminal.png%"dorothy" Exec exec xterm -geometry 80x37+30+60 -T "screen : dorothy" -e screen -x -c $HOME/.screenrc-dorothy -R dorothy I usually create a new screen config for each project that launches shells in the right directories, etc. For example, here's my .screenrc-dorothy: chdir $HOME/projects/dorothy/lib/dorothy screen -t lib 1 zsh chdir $HOME/projects/dorothy/test/dorothy screen -t test 2 zsh chdir $HOME/projects/dorothy/ext screen -t ext 3 zsh chdir $HOME/projects/dorothy screen -t irb 4 zsh at irb# eval 'stuff "irb -r dorothy\015"' chdir $HOME/projects/dorothy screen -t zsh 0 zsh hardstatus alwayslastline "%{rk}%H %{gk}%c %{yk}%M%d %{wk}%?%-Lw%?%{bw}%n*%f %t%?(%u)%?%{wk}%?%+Lw%?" That gives me shells in the directories I'm likely to be working from, and starts an irb session in another shell. I guess this is only newsworthy if you're not the type to customize your environment to your liking. Well, that and the fact that gnu screen is somewhat difficult to learn and researching it is a pain because "screen" is such a poor, generic name for a project. I'd love to see this turn into a thread of neat things that can be done with gnu screen.