31–40 of 86 posts
Guake, which provides a Quake like terminal and quick and easy access to a terminal using the F12 key. Plus, it supports anti-aliased fonts and multiple tabs. http://trac.guake-terminal.org/ On my Mac at work I use Visor. http://docs.blacktree.com/visor/visor
I only discovered it due to my boss' "install everything" cygwin policy, as it's in their repo and its installer puts a link on your desktop.
PuTTY is bad enough as an SSH client, much less its crap terminal emulation. Whoever at Microsoft that keeps making the decision to ship cmd.exe again needs to be hanged in public square.
rxvt-unicode with its Perl API [1] and rather amazing list of Perl extensions [2] on Linux OSes, puttycyg on Cygwin. (I recommend puttycyg if you've been using rxvt on Cygwin. Being able to type Unicode characters is an amazingly exhilarating experience, especially if you're lonely.) [1]: http://pod.tst.eu/http://cvs.schmorp.de/rxvt-unicode/src/urx... [2]: http://software.schmorp.de/pkg/rxvt-unicode.html
For example, xterm sends '\e[H' for Home by default, while puttycyg (and xterm in VT220 mode) sends '\e[1~' and rxvt sends '\e[7~'.
I can configure some overrides in .inputrc, but sooner or later these start to conflict with one another if I want to be able to switch at will. Seems easier to stick to rxvt, and know that my preferences in ~/.Xdefaults also apply on non-Windows boxes.
(Actual answer: aterm for the transparency feature.)
Actually, in recent years, it seems like gnome has gotten harder and harder to use for an expert in all aspects...I occasionally have to work on a gnome machine and it's pure hell trying to figure out how to get simple stuff to work.
Of course, perhaps this is their goal in any case: target n00bs and grandmas to increase marketshare. If so, I'm perfectly fine with that =)
Terminal.app as of OS X 10.5 is my favorite terminal. I like to use rxvt under Cygwin.
Try out iTerm sometime. Much, much faster and lighter than Terminal.app. I switched to iTerm when Terminal.app crashed while compiling Haiku ... twice. The problem, I believe, was the large amount of compiler output.
Earlier quoted context omitted.
Try out iTerm sometime. Much, much faster and lighter than Terminal.app. I switched to iTerm when Terminal.app crashed while compiling Haiku ... twice. The problem, I believe, was the large amount of compiler output.
I used iTerm before Leopard, but it crashed at least once a week, and sometimes it would just forget settings, and it used up an insane amount of resources if you left it open for a few days (and shutting down all my ssh sessions and restarting them is not my idea of a good time, nor is trying to figure out where I put this server or that server in the tab list; I like them to stay at the same position so I don't hav…
Try GNU screen or tmux.
Earlier quoted context omitted.
Try out iTerm sometime. Much, much faster and lighter than Terminal.app. I switched to iTerm when Terminal.app crashed while compiling Haiku ... twice. The problem, I believe, was the large amount of compiler output.
I recently switched back to iTerm due to its full screen option, which I use when I want to really concentrate and/or see some really wide output. Back in the Panther/Tiger days it used to crash rather frequently, seems a lot better now; I haven't had it crash in some time. I can tolerate the occasional crash because my sessions are always protected by screen.
Gnome Terminal because of its text smoothing (and because it adheres to a set of human interface guidelines).
I'd recommend mrxvt, a superset of rxvt. It's lighter, has support for tabs, fonts, transparency, etc.
Rxvt, normally on Cygwin. If I had more use for Unicode in practice, I'd use urxvt on non-Cygwin. Also, when ssh into remote boxes, I often use screen, which effectively ends up being a pretty crappy terminal - major failure mode is loss of scrollback buffer, Ctrl-A ESC notwithstanding.
Huh? The loss of the scrollback buffer sucks... except for that other scrollback buffer?