OS X and xterms

ziggy on 2002-07-11T21:19:56

The standard Terminal.app in OS X is nice, but it's not a really great xterm. It has the same kinds of display problems as the standard console in Win*: it can't show threads in mutt properly, nor does it handle prompts correctly within the debugger or CPAN shells. (Likely due to a terminal issue with Term::Readline or somesuch.)

The lazy solution: run X using OroborOSX instead of the ugly, utilitarian XDarwin (which doesn't use a window manager really, let alone one with an Aqua-ish theme).

That really makes this iBook feel like $HOME. :-)


It's funny how slow Terminal.app is

Elian on 2002-07-11T21:35:38

An eterm, with textured background, is about four times faster displaying stuff than Terminal is. Almost pathetic, really...

Re:It's funny how slow Terminal.app is

ziggy on 2002-07-11T21:42:36

It's also annoying how much memory Terminal.app consumes. Right now, XDarwin is taking up ~64MB (typical), and each xterm is taking up another 1MB or so. The window manager has transparency turned on for non-active windows, which must add something to the mix. All in all, that seems much more reasonable (modulo the memory for XDarwin).