||[Feb. 18th, 2003|11:02 pm]
gnome-terminal is a piece of shit. (currently using 2.2.1, but every prior version has also been a piece of shit too.)|
unfortunately, it's one of the best pieces of shit out there. it supports profiles, tabs, Xft/fontconfig, utf-8.... just wish it wouldn't randomly do stupid stuff all the time.
i've tried konsole (KDE) ... it's finicky too, especially dealing with fonts. and i couldn't figure out its profiles.
newer xterms can do fonts well with freetype, but the width of characters is all messed up... i'm probably missing a billion obscure command line options.
i guess i'll stick with gnome-terminal for now? :-/
2003-02-18 11:59 pm (UTC)
tried the terminal emulator that comes with Enlightenment? I think it's just eterm..
2003-02-19 01:48 am (UTC)
What's wrong with it? It works flawlessly for me.
You have to get the one from either experimental or unstable to get the one based on vte, and then you have to configure your fonts properly (monospace truetype fonts are rare), but then it's quite good. I hear reports of it being too slow but I've never noticed, and apparently many of those reports are related to broken binary-only X drivers from nVidia(?).
2003-02-19 04:35 am (UTC)
M-x shell, dude. It's the only way to fly.
The worst thing I've found in gnome-terminal are the display/rendering bugs -- sometimes it leaves characters which don't scroll, regardless of reset, and
which aren't really there, either -- cover, uncover redraw doesn't fix. Usually
it is parts of characters, or underscores, or whatever.
gnome-terminal sucks the least. I think it is presently the mutt of xterm replacements.
(a 2003 version of the "geek code" which compresses info on which MTA, MUA, term,
desktop environment, editor, web browser, OS, hardware platform, etc. would serve
the holy wars well, I think)
2003-02-20 12:06 pm (UTC)
xterm -bg black -fg white -fn vga
Saying gnome-terminal sucks is like complaining that Windows crashes too much or uses up too many resources.
But seriously, if gnome-terminal really does support UTF-8, that's news to me, as I've yet to see it handle any kind of > 7-bit character properly. It barfs with a "WARNING **: No handler for control sequence 'device-control-string' defined." any time it sees or I try to input an extended character (even something as simple as ñ), and when it sees such a thing, it won't even display the character on the screen, completely screwing up viewing of a file which has a lot of those.