From owner-freebsd-stable Sun May 5 12:31:54 2002 Delivered-To: freebsd-stable@freebsd.org Received: from CRWdog.demon.co.uk (p69-199.acedsl.com [66.114.69.199]) by hub.freebsd.org (Postfix) with ESMTP id A93A237B404 for ; Sun, 5 May 2002 12:31:49 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by CRWdog.demon.co.uk (Postfix) with ESMTP id C60593E14 for ; Sun, 5 May 2002 15:31:47 -0400 (EDT) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: stable@FreeBSD.ORG Subject: Re: cvs commit: ports/mail/mutt-devel Makefile In-Reply-To: Your message of "Sun, 05 May 2002 14:39:18 EDT." <20020505183918.GA27835@pir.net> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_-696087446P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Sun, 05 May 2002 15:31:47 -0400 From: Andy Sparrow Message-Id: <20020505193147.C60593E14@CRWdog.demon.co.uk> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --==_Exmh_-696087446P Content-Type: text/plain; charset=us-ascii > "Jose M. Alcaide" probably said: > > In ~/.Xdefaults: > > *customization: -color > > And in app-defaults/XTerm-color: > > *termName: xterm-color Well, that's interesting, because I've had that first hack for some years, and I add the contents of $APPDEFAULTS/XTerm-color to my local ~/XTerm file, but this stopped working for me about 6-7 months and two X updates ago. I don't want to set TERM=xterm-color for reasons already stated. > > (you can add "XTerm*termName: xterm-color" to ~/.Xdefaults instead) > > > > Actually, I think that "*termName: xterm-color" should be always defined > > in app-defaults/XTerm-color. Maybe the x11/XFree86-4-clients port should > > apply a patch for doing that, given that FreeBSD has both "xterm" and > > "xterm-color" entries in termcap(5). Both of which are specifically stated to be incorrect (with an explanation why) by the maintainer of XFree86 xterm on his web page. XFree86's 'xterm' is a color xterm, and has been for years. We don't ship their termcap entry. Substituting the XFree86 termcap/terminfo entries for ours apparently fixes the currently broken behaviour. As we apparently have a policy of shipping whatever XFree86 ship: On this topic in <200007190145.SAA20697@mass.osd.bsdi.com>, Mike Smith said: | We've generally maintained that we should ship whatever the XFree86 | people send us. What's their take on this? I don't understand why this is presently borken. > Other OSen do not have xterm-color, though (as has already been > mentioned, Solaris), so this breaks as soon as you ssh to one of these > remote machines. As someone who runs Solaris servers from a FreeBSD > desktop I do this a lot. What he said :) Also, some OS's have an entry for 'xterm-color' that is NOT the XFree86 xterm, but an obsolete xterm variant, and this will also break. > If you tried to make this the default you'd get a lot of very annoyed > people. Exactly. Regards, AS --==_Exmh_-696087446P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: Exmh version 2.5 07/13/2001 iD8DBQE81YijPHh895bDXeQRAswUAKCx89VXczsIccMfmH59BsUpJth0PQCgslSt Qhxam0ZnZjGHTQ+e81k9CQU= =e8EY -----END PGP SIGNATURE----- --==_Exmh_-696087446P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message