51–60 of 103 posts
screen device baud
ex:
screen /dev/tty.usbserial-FTDPZOEJ 115200
Very useful for embedded system hackers and others who still need to speak RS-232.
In the same vein, if you use a repl on a remote machine you should check out detachtty if you're not already using it. It's particularly nice for use within emacs because it doesn't eat the whole screen and it doesn't eat ^A.
You can send ^a to a window in screen by typing "^a a" - I do this everyday using emacs inside of screen. It becomes second nature.
In the same vein, if you use a repl on a remote machine you should check out detachtty if you're not already using it. It's particularly nice for use within emacs because it doesn't eat the whole screen and it doesn't eat ^A.
fwiw, screen doesn't "eat ^A" You can send ^a to a window in screen by typing "^a a" - I do this everyday using emacs inside of screen. It becomes second nature.
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)
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...
Earlier quoted context omitted.
` cannot be used since in terminal C + ` or C + SPC or C + @ translates into same thing(only allowed characters are @ [ \ ] ^ and _ ). I personally prefer using \
Oh, I'm using just ` , not C-`. It's like hitting ESC in vi. (I also noticed that space and shift-space are indistinguishable, which is a bit annoying because in Emacs I use S-spc for languages with lots_of_soft_spacing or-several-words-joined-with-dashes.)
whereas you'd have thought it would be just escape `
Earlier quoted context omitted.
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 d…
Your second scenario can be handled with nohup from within a vanilla ssh session.
Earlier quoted context omitted.
Oh, I'm using just ` , not C-`. It's like hitting ESC in vi. (I also noticed that space and shift-space are indistinguishable, which is a bit annoying because in Emacs I use S-spc for languages with lots_of_soft_spacing or-several-words-joined-with-dashes.)
Readers - I found the .screenrc change for this not-entirely-obvious. You need to say escape `` whereas you'd have thought it would be just escape `
escape `~
Earlier quoted context omitted.
I'm using C-z, but it's sort of an awkward key to use.
Changing caps lock to control helps. Switching to dvorak helps even more. I kid.
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)
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).