If I understand correctly, it is newsworthy because it provides a method by which you can automatically go to a particular session and/or shell in that session by running just one command on your local machine in which you specify the Screen title of that session/shell.
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:
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.
ssh yourserver -t "screen -D -RR"
doesnt't allow you use screen from multiple xterms
if you use
ssh -t yourserver screen -S main -xRR -p windowname -q
as was used in the post, you get to use, multiple xterms all connecting to the same session.
I think you guys are being a bit harsh on this article. Its not as if it was saying "ssh to remote and run screen" was something new. It does provide some useful hints on .screenrc setup and while running a script to connect to the remote screen may not be for everyone it is useful.
I find the main problem with running screen over ssh is that the remote screen doesn't interact well with the local one. I tend to just have multiple local ssh sessions and not run screen remotely, but it isn't ideal.
13 comments
[ 97.3 ms ] story [ 227 ms ] threadThe article seems like needless complication.
And, as thras pointed out, it's needlessly complicated. All you need to do is:
ssh yourserver -t "screen -D -RR"
And you'll have a new screen session, or reattach to your old screen session, however you left it set up.
If you're on a mac and you want to set up a different background colour for each server, check out my tutorial at: http://www.swombat.com/setting-up-terminalapp-with-tr-0
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.
Really. I find it pretty easy to use search terms like "gnu screen" or "screenrc" to get lots of results in Google...
if you use ssh -t yourserver screen -S main -xRR -p windowname -q as was used in the post, you get to use, multiple xterms all connecting to the same session.
I put escape ^Ww in my local .screenrc, and this alleviates most if not all the problems with running screen on both the local and remote machines.