|brad's quick software review
||[Mar. 16th, 2004|04:06 pm]
screen + gnome-terminal = still a piece of shit|
(not sure who to blame, but I'd say gnome-terminal, since it's been on my shitlist for years...)
I loved gnome-terminal until gnome 2 came out...
All I can say is libzvt redraw bugs... But my experience with those is from Gnome 1.x. I think I've avoided gnome-terminal in Gnome 2.x so far. :-)
2004-03-16 04:43 pm (UTC)
Screen + konsole = useable.
me + beer = sysadminable.
Your blame is well-founded.
screen works just fine with TERM=vt220, and even TERM=xterm provided Linux isn't involved.
2004-03-16 05:01 pm (UTC)
... note that screen doesn't give a shit, let alone two, about gnome-terminal, konsole, xterm, or eterm. It only cares about the TERM environment variable or, more accurately, what's in your termcap for the value of TERM. (Which is why TERM=xterm and Linux don't mix well; the definition for xterm in various distros' termcap keeps changing. xterm-old might dtRt.)
So, for me, using irssi in gnome-terminal in screen (er, swap the last two, I guess), if you use tabs, it will fuck up the redraw badly and screw things up, but without tabs, if no tabs have ever been opened in that window, it works great..
Is this a stability issue?
At college, on RH8 machines, gnome-terminal would suck up memory and slow to a halt.
However, my laptop doesn't seem to give any problems.
Someone suggested this might have to do with the sub-pixel font anti-aliasing thingy.
(tho i use a tabbed wm (fluxbox) that provides the GNOME-Terminal-style tab-fast-switching that I need)
if you were using screen, you wouldn't care about tabs
2004-03-17 10:38 am (UTC)
Ah, you know screen. Cool points.
Oh, and Oregon. :-)
well exactly- so why use gnome-terminal instead of a lightweight aterm/eterm/xterm?
I can only assume that its because gnome-terminal is being used with it's own internal tabs? (ie: not in "screen" fashion)