Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Well... | 15 comments | Create New Account
Click here to return to the 'Well...' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Well...
Authored by: robg on Mar 03, '03 11:37:19AM

... I'm probably an idiot for saying this, but I find 'screen' way too complicated to use for anything beyond the simplest level -- I use it when I want to start a remote download and then disconnect, but that's it. Anything beyond that, and I find myself quickly lost in a mess of screen changes -- I can't remember what I've started, what I detached, what's not started, etc. I know I can list them, but that's a pain in the but, and cycling through them to get to the one I want is a royal pain. That's why I don't use screen instead...

With Terminal, I usually open 5 to 10 windows; with iTerm, that's 5 to 10 tabs instead. I can see them all, I know where they all are, and they're easy to manage. That's what I liked about it.

As an aside, it certainly wasn't slow in my testing of it this weekend -- I noticed no speed differences at all between it and Terminal.

I probably won't switch to it full-time unless some of the glitches are worked out, but it's a nice change from the multi-window Terminal.

I'm not sure what's wrong with having innovation and choice; those that prefer screen can use it, those of us that are more visual (and/or dumber, if you prefer) can stick with either multiple Terminal windows, GLTerm, or something like iTerm.

-rob.



[ Reply to This | # ]
screen window list
Authored by: r0adrage on Mar 03, '03 03:28:25PM
To help keep track of screen sessions, you can use the status line. Put the following in your .screenrc:

termcapinfo vt100* 'hs:ts=\E]2;:fs=\007:ds=\E]0;screen\007'
defhstatus "screen:^Ew"

(all characters are literal, ie. ^E is a carat (^) and an E, not control-E) and it will set the titlebar to list all windows by number and title. the vt100 line is snagged from the screen xterm hints, and tells screen to use the titlebar as the status line. The second line sets up the status to show the list of windows. The current screen-window will have a * by its number. Its still not tabs, but it is easier than trying to remember which window is which. Now, if anyone knows how to dynamically change the title of a screen window to be the currently running program, please let me know!

[ Reply to This | # ]

screen window list
Authored by: jyncroft on Mar 04, '03 11:13:10AM

I can't get this to work...

$TERM=vt100
$TERMCAP=<some strange text, 4 characters>

That's before invoking screen. Afterwards...

$TERM=screen-w
$TERMCAP=<a lot of stuff, all readable>

with your two lines in my .screenrc file, invoking screen just spews out the following on the screen...

E]2;screen:0* zsh07E]0;screen07E]2;screen:0* zsh07

Is there a problem with the lines that got posted vs what should be posted?



[ Reply to This | # ]
screen window list
Authored by: nivex on Mar 29, '06 01:08:16PM
The code posted somehow stripped the backslash characters and the chars following it. Here's what I have in my screenrc that works:

termcapinfo xterm* 'hs:ts=\E]2;:fs=\007:ds=\E]0;screen\007'
This looks OK in preview... hopefully it makes it to post OK.

[ Reply to This | # ]
Well...
Authored by: daveedvdv on Mar 03, '03 11:53:26PM

Agreed. The speed of iTerm is usually not objectionable (except for a quirk in a recent version, but they fixed it quickly). The interface is much more intuitive than screens' and the status display is better even than konsole's (which was probably the app I missed most when switching from Linux to MacOS X).

I've beeny using iTerm full-time as my terminal application (mostly running simple bash and ksh sessions; vim works fine too). It seems to be developed pretty actively these days.



[ Reply to This | # ]
Well...
Authored by: krishna on Aug 01, '03 02:58:41PM

--- begin some idiot's comments ---
... I'm probably an idiot for saying this, but I find 'screen' way too complicated to use for anything beyond the simplest level -- I use it when I want to start a remote download and then disconnect, but that's it. Anything beyond that, and I find myself quickly lost in a mess of screen changes
--- end some idiot's comments ---

Always good to meet a fellow idiot (ref: http://bugs.kde.org/show_bug.cgi?id=58868 :-). Let's rephrase the question: is there a good reason why a detachable-screen terminal emulator with piles and piles of magic keystroke commands (making it usable via ssh session or via x-terminal) *shouldn't* make use of menus, context menus, tabs (i.e., the full range of GUI elements) when they're available?

Emacs took until version 18-ish to provide a mousable menu for the common keystroke commands, immediately improving its usability by both keyboarders and mousers. Shouldn't screen learn from that lesson?



[ Reply to This | # ]