News for hackers. Stuff that matters.
Re:GNU Screen - A Hacker's Ideal Terminal by tlrobinson on Monday September 28, 2009 @03:07PM (#848995)
I've been satisfied with just using multiple tabs in Terminal.app in OS X, but I'm curious if anyone has switched from that solution to screen and wouldn't go back? (for local use in particular)
Re:GNU Screen - A Hacker's Ideal Terminal by potatolicious on Monday September 28, 2009 @03:24PM (#849033)
I use screen constantly and would never go back. The detachability is incredibly useful. Say I had to go to a meeting - I shut my laptop and it goes to sleep. This would normally kill any SSH session (and thus leave vim swap files lying about in my case)... but with screen I can just pick up where I left off last time.

It's also great if you want to run something big - say a job that would take 5 hours. I'm free to do whatever I want without fear that killing my ssh session will also kill the job.

Re:GNU Screen - A Hacker's Ideal Terminal by scott_s on Monday September 28, 2009 @03:40PM (#849063)
Your second scenario can be handled with nohup from within a vanilla ssh session.
Re:GNU Screen - A Hacker's Ideal Terminal by graywh on Monday September 28, 2009 @04:45PM (#849199)
There's also disown, for that matter, but how can you re-connect to the process?
Re:GNU Screen - A Hacker's Ideal Terminal by silentbicycle on Monday September 28, 2009 @03:26PM (#849037)
> run something big - say a job that would take 5 hours

The monitor function can also notify you when there's activity or 30 sec. silence in a window, too. :)

Re:GNU Screen - A Hacker's Ideal Terminal by sofal on Monday September 28, 2009 @05:15PM (#849239)
I've switched from Terminal.app tabs to screen for a couple of reasons:

1) It's obvious why you'd want this for remote sessions, and I want a consistent feel whether I'm sshing into remote machines or just on my local machine.

2) I like to allocate a different screen session for each project. I can use the Terminal.app tabs to differentiate between these and between remote sessions on other machines. I could technically use multiple Terminal.app windows instead, but meh.

One thing I've found to be annoying: I can't get gnuplot to work from within a screen window (using the default AquaTerm output).

Re:GNU Screen - A Hacker's Ideal Terminal by pyre on Monday September 28, 2009 @05:52PM (#849314)
I know that there was a patch (a long time ago ~2006) for gnome-terminal that made it 'screen aware' so that each screen 'window' was a gnome-terminal tab.
Re:GNU Screen - A Hacker's Ideal Terminal by EAMiller on Monday September 28, 2009 @04:17PM (#849143)
I got frustrated with tabs in Terminal.app because of the keyboard shortcuts : Shift+Apple+arrows

In screen I use ^a, " to get a list of screens, then j/k to pick a screen. That may not seem like a win, but it keeps my fingers on the home keys, and feels smoother.

That and the fact that I split windows in screen fairly often means I won't go back to terminal tabs...

Re:GNU Screen - A Hacker's Ideal Terminal by sjs on Monday September 28, 2009 @03:35PM (#849054)
You can copy and paste between terminals with the keyboard. This alone should be reason enough.