Comments on: The Mac OS X Terminal Holy Grail: mrxvt http://eseth.org/2007/mrxvt Making close friends suffer through crappy writing since aught-one. Wed, 21 May 2008 19:14:36 +0000 http://wordpress.org/?v=2.0.2 by: Steve Yegge http://eseth.org/2007/mrxvt#comment-22326 Fri, 25 Apr 2008 20:10:36 +0000 http://eseth.org/2007/mrxvt#comment-22326 <p>Thanks for the tip - mrxvt is quite a bit faster than /usr/X11/bin/xterm on Leopard, running on a MacBook Pro driving a 30-inch at 2560x1600 and the laptop display at 1440x900 (hence: video card working hard), running Emacs in an ssh session in 256-color mode. mrxvt is downright snappy, even when it's maximized.</p> <p>However, mrxvt on my setup has a showstopper bug - using antialiased Monaco 12-pt, the bold characters are wider than the nonbold; showing "abcdefghijklmnopqrstuvwxyz ABCDEFGHIJKLMNOPQRSTUVWXYZ" in both weights has the bold 'S' lining up with the nonbold 'Z'. This results in greebles and general unreadability in apps mixing bold and nonbold characters. The stock xterm app doesn't have this problem, so I'm stuck using it (even though it's substantially slower on refreshes) until I can find a fix.</p> <p>I'm looking for a way to disable bold fonts in the X session altogether as a workaround. Haven't found it yet, but I'm sure there's a way.</p> Thanks for the tip - mrxvt is quite a bit faster than /usr/X11/bin/xterm on Leopard, running on a MacBook Pro driving a 30-inch at 2560x1600 and the laptop display at 1440x900 (hence: video card working hard), running Emacs in an ssh session in 256-color mode. mrxvt is downright snappy, even when it’s maximized.

However, mrxvt on my setup has a showstopper bug - using antialiased Monaco 12-pt, the bold characters are wider than the nonbold; showing “abcdefghijklmnopqrstuvwxyz ABCDEFGHIJKLMNOPQRSTUVWXYZ” in both weights has the bold ‘S’ lining up with the nonbold ‘Z’. This results in greebles and general unreadability in apps mixing bold and nonbold characters. The stock xterm app doesn’t have this problem, so I’m stuck using it (even though it’s substantially slower on refreshes) until I can find a fix.

I’m looking for a way to disable bold fonts in the X session altogether as a workaround. Haven’t found it yet, but I’m sure there’s a way.

]]> by: whiteinge http://eseth.org/2007/mrxvt#comment-22050 Wed, 02 Apr 2008 04:59:02 +0000 http://eseth.org/2007/mrxvt#comment-22050 <p>@Alan, one word: detaching. Also you can run a nested remote screen in a local screen. Anything else is just ridiculous by comparison. :-)</p> <p>@David, no it looks like Leopard's Terminal 2 does not support 256-colors out of the box. Totally weak.</p> @Alan, one word: detaching. Also you can run a nested remote screen in a local screen. Anything else is just ridiculous by comparison. :-)

@David, no it looks like Leopard’s Terminal 2 does not support 256-colors out of the box. Totally weak.

]]> by: David V http://eseth.org/2007/mrxvt#comment-21503 Thu, 14 Feb 2008 02:29:53 +0000 http://eseth.org/2007/mrxvt#comment-21503 <p>guh, I meant to say "fiddling with it for 15 minutes at the mac STORE"</p> guh, I meant to say “fiddling with it for 15 minutes at the mac STORE”

]]> by: David V http://eseth.org/2007/mrxvt#comment-21502 Thu, 14 Feb 2008 02:28:32 +0000 http://eseth.org/2007/mrxvt#comment-21502 <p>Does Terminal in Leopard really support 256 colors? I can't find confirmation of this fact on apple's site, and fiddling with it for 15 minutes at the mac did not confirm this for me. In fact I'm more convinced that there is still a maximum 16 color limit in Terminal.app. Does one need to do anything special to enable this feature in Leopard? </p> <p>It's sad but I think I might spend 139$ on it just for that one feature. iTerm doesn't quite cut it for me and I don't like the X11 integration on the mac much either.</p> Does Terminal in Leopard really support 256 colors? I can’t find confirmation of this fact on apple’s site, and fiddling with it for 15 minutes at the mac did not confirm this for me. In fact I’m more convinced that there is still a maximum 16 color limit in Terminal.app. Does one need to do anything special to enable this feature in Leopard?

It’s sad but I think I might spend 139$ on it just for that one feature. iTerm doesn’t quite cut it for me and I don’t like the X11 integration on the mac much either.

]]> by: Alan Jurgensen http://eseth.org/2007/mrxvt#comment-20733 Tue, 11 Dec 2007 16:48:39 +0000 http://eseth.org/2007/mrxvt#comment-20733 <p>Why use screen when you can use mrxvt tabs? there are hot keys to jump from tab to tab... also since I ssh to a bazillion boxes I support, I have some helpers to set the tab title, or the file i'm vim-ing, etc. Setting a pixmap background is also the cats ass.</p> Why use screen when you can use mrxvt tabs? there are hot keys to jump from tab to tab… also since I ssh to a bazillion boxes I support, I have some helpers to set the tab title, or the file i’m vim-ing, etc. Setting a pixmap background is also the cats ass.

]]> by: whiteinge http://eseth.org/2007/mrxvt#comment-18701 Wed, 26 Sep 2007 22:26:24 +0000 http://eseth.org/2007/mrxvt#comment-18701 <p>It's a fair complaint; I am also looking forward to unicode support in mrxvt. Although I think it is a mistake to take unicode support for granted in a terminal environment. There is so much legacy code out there, it will be a long while still before command-line unicode becomes commonplace. For example, I see command-line encoding problems almost daily as I work (as a web developer) -- even when using Terminal.app or other UTF-aware terminals.</p> It’s a fair complaint; I am also looking forward to unicode support in mrxvt. Although I think it is a mistake to take unicode support for granted in a terminal environment. There is so much legacy code out there, it will be a long while still before command-line unicode becomes commonplace. For example, I see command-line encoding problems almost daily as I work (as a web developer) — even when using Terminal.app or other UTF-aware terminals.

]]> by: axolx http://eseth.org/2007/mrxvt#comment-18700 Wed, 26 Sep 2007 21:53:23 +0000 http://eseth.org/2007/mrxvt#comment-18700 <p>NO UTF8 SUPPORT? Thats is unacceptable for me in 21st century computing. You should note that somewhere in your article, as I took it for granted and spent a bunch of time setting mrxvt in my system only to find out it lacks UTF8 support.</p> NO UTF8 SUPPORT? Thats is unacceptable for me in 21st century computing. You should note that somewhere in your article, as I took it for granted and spent a bunch of time setting mrxvt in my system only to find out it lacks UTF8 support.

]]> by: duckpond http://eseth.org/2007/mrxvt#comment-17145 Fri, 27 Jul 2007 21:02:33 +0000 http://eseth.org/2007/mrxvt#comment-17145 <p>mrxvt install was a success, vim and emacs can all work on 256 colors mode. for emacs, the xterm-256color.el was not there by default, you'll need to drop a copy to the $EMACS_HOME/lisp/term/ directory.</p> <p>also installed ncursesw via MacPorts (now called DarwinPorts?), and terminfo for xterm-256color were installed by the package. I tried:</p> <p>TERM=xterm-256color vim</p> <p>just in the regular Terminal.app, vim then gave me a blinking screen, is the terminfo can only be recognized by X11 applications?</p> <p>thanks,</p> mrxvt install was a success, vim and emacs can all work on 256 colors mode. for emacs, the xterm-256color.el was not there by default, you’ll need to drop a copy to the $EMACS_HOME/lisp/term/ directory.

also installed ncursesw via MacPorts (now called DarwinPorts?), and terminfo for xterm-256color were installed by the package. I tried:

TERM=xterm-256color vim

just in the regular Terminal.app, vim then gave me a blinking screen, is the terminfo can only be recognized by X11 applications?

thanks,

]]> by: whiteinge http://eseth.org/2007/mrxvt#comment-17088 Thu, 26 Jul 2007 06:45:01 +0000 http://eseth.org/2007/mrxvt#comment-17088 <p>You can try copying the xterm-256color file from one computer to the other. That worked for me for a while with screen-256color until MacPorts updated their GNU screen package.</p> <p>In direct answer to your question: it appears that the xterm-256color file belongs to the ncurses package in MacPorts (ncursesw). (I'm not sure about Fink.)</p> You can try copying the xterm-256color file from one computer to the other. That worked for me for a while with screen-256color until MacPorts updated their GNU screen package.

In direct answer to your question: it appears that the xterm-256color file belongs to the ncurses package in MacPorts (ncursesw). (I’m not sure about Fink.)

]]> by: duckpond http://eseth.org/2007/mrxvt#comment-17050 Wed, 25 Jul 2007 15:43:50 +0000 http://eseth.org/2007/mrxvt#comment-17050 <p>One of my office machine has the xterm-256color entry in /usr/share/terminfo/78/, but in my newly build osx86, I don't see ther terminfo xterm-256color anywhere, so I am guessing maybe I should install or upgrade some package to have that particular terminfo? what package should I reinstall?</p> One of my office machine has the xterm-256color entry in /usr/share/terminfo/78/, but in my newly build osx86, I don’t see ther terminfo xterm-256color anywhere, so I am guessing maybe I should install or upgrade some package to have that particular terminfo? what package should I reinstall?

]]>