Date: Sat, 04 May 2002 16:15:16 -0400 From: Andy Sparrow <spadger@best.com> To: Martin Karlsson <martin.karlsson@visit.se> Cc: stable@FreeBSD.ORG Subject: Re: cvs commit: ports/mail/mutt-devel Makefile Message-ID: <20020504201516.BA9CA3E14@CRWdog.demon.co.uk> In-Reply-To: Message from Martin Karlsson <martin.karlsson@visit.se> of "Sat, 04 May 2002 20:26:50 %2B0200." <20020504182649.GA1168@foo31-146.visit.se>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] > * Andy Sparrow <spadger@best.com> [2002-05-04 12.55 -0400]: > [...snip...] > > However, the color customizations discussed in the XTerm web page: > > > > http://dickey.his.com/xterm/xterm.faq.html#my_xdefaults > > > > haven't worked for some time in FreeBSD, for me anyway. (They used to, but > > stopped after a commit sometime in 2001, IIRC). > > I put a "real" xterm termcap in front of the freebsd one, and > rebuilt the termcap.db. Works for me. Yes, but... Maintaining local hacks like this is so painful when you've accumulated a bunch of them... Much nicer to run an freshly-sup'd version without local hacks. > > I run so few color-based text apps that it's not worth the hassle to sort it > > out (although it is somewhat irritating that we appear to be Doing It Wrong, > > after it used to work). > > I agree. Why is this happening anyway? Last thread I saw on the topic turned into a clash of commiter privs (as in "I have them, it'll be this way"). Most people want to have local xterms Just Work. In mono by default, but display color if you run up sysinstall/mutt/ports dialog etc. in an xterm. They also want remote xterms to display correctly on their local screens. This used to work perfectly with the color customizations in ~/.Xdefaults and Xterm-color (an acceptable hack, IMHO), but this no longer works. Setting TERM=xterm-color (or some other wonky, non-standard value) to get this is not really acceptable (for me at least). As a gigging SA, I work on 100's of systems, generally for relatively short periods of time. I often use my laptop for this (I'm not about to put my private SSH/GPG keys on a networked filesystem, but I'll happily put the public ones in authorized_keys2 etc.). I'm also not about to start frobbing said systems to understand 'xterm-color' or 'cons25' term types (another annoyance, but 'ansi' works well enough for most things), 'coz this just doesn't scale. Slowaris (for example) /is/ an Industry Standard. Making it more difficult to Just Work with these systems doen't help the cause. That other OS that ends in "nux" (I have to work with this too) does a better job in this respect. > >Feh. I believe I've seen at least one PR on the subject, although I > >can't find it now. > > 35092 perhaps? Quite possibly, although I thought it was another one. Glad I'm not the only one who's seeing this (misery loves company ;-). I think I've just talked myself into doing the local hack - but it seems unnecessary to me, and it pains me when other people say of my favorite OS: : The xterm-color value for $TERM is a bad choice for XFree86 xterm : because it is commonly used for a terminfo entry which happens to : not support bce. Complicating matters, FreeBSD (after dithering for : a few years on the matter) has a bastardized version which implies : the opposite sense of bce, (because it uses SGR 39 and 49), but : does not set it. Present behaviour just seems flat-out wrong to me. My $0.25 worth. Regards, AS [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: Exmh version 2.5 07/13/2001 iD8DBQE81EFUPHh895bDXeQRAkGFAKDIPtOUW9MNkMXUKcGWTtQ7JrFMBQCeOTyB 9EyTXaJ1UPEzRFOukIKAikk= =7ue9 -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020504201516.BA9CA3E14>