5 ms·
On the Mac, I use MacTelnet, even as a local terminal. It has an almost ridiculous number of features (compared to Terminal.app or iTerm, anyway), and is very
by makecheck 17y ago
On the Mac, I use MacTelnet, even as a local terminal. It has an almost ridiculous number of features (compared to Terminal.app or iTerm, anyway), and is very configurable. The main problems are that it is mainly vt100/partial-xterm, and is a beta.
On Linux or Solaris, I use "aterm". It works as well as xterm or rxvt. But it has a lot of nice interface tweaks, such as NeXT-style scrollbars, pseudo-transparency, more intelligent text selection (IMHO), and a way to change colors when inactive.
On Windows, I don't run much locally (since not a lot of useful command-line tools come with Windows). So my terminal work tends to be over SSH to a machine that has real tools. :) I use PuTTY for SSH, and it works very well. My main issue is that it seems unnecessarily hard to do certain things, e.g. copy/paste.
- apotheon 17y agoI used to use aterm, but one thing drove me to change -- Unicode support. Now, I use rxvt-unicode. Since making the move, though, I've grown to love rxvt-unicode's daemon mode and discovered that pseudo-transparency works better than it did on aterm. I mention my reasons for choosing rxvt-unicode over other terminal emulators here: http://sob.apotheon.org/?p=451 http://sob.apotheon.org/?p=451
- pyre 17y agorxvt-unicode also supports true transparency when you have a composite manager active.
- apotheon 17y agoTrue -- but I like the way AHWM works more than the way Compiz works, so that's not really a concern for me.
- pyre 17y agoYou could also try to stomach xcompmgr for compositing...
- apotheon 17y agoWikipedia's information about it confuses me. It says xcompmgr is a window manager, but it says it "does not replace any existing window manager". Does this mean it would replace AHWM, or that it would just add compositing to AHWM -- or something else entirely? Also . . . what about it is difficult to "stomach"?
- pyre 17y agoxcompmgr is a Composite manager. It will run along side any other window manager (that doesn't already do compositing... this excludes Compiz, newer KWin, Xfce4's window manager, but exactly what would happen if you tried to run xcompmgr and Compiz at the same time I don't know). It just does things like add drop shadows around windows and enable true transparency. {edit} You can configure the drop-shadows or disable them through command-line options {/edit} I said 'stomach' because xcompmgr has been unstable at times in my experience. IIRC, none of the xcompmgr crashes have taken down X11 or the window manager. I have not used it in a while though so it may have changed, but I was under the impression that it doesn't get much work done on it. It's original goal was just to be a reference/example implementation of the compositing extension for X. I could be wrong though and it might be in a more stable state now. If anything you might be motivated to see if there is a way to run it with debugging information. I can't imagine it's highly complex in the way that I assume Compiz is. It might be fairly easy to do some fixing up of it, as long as a person is motivated to look into it.
- apotheon 17y agoThanks for the information. I think I'll give that a look on a test system, if only to see whether I care enough to bother.