From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.43) id 1E7Sda-0004N6-T7 for garchives@archives.gentoo.org; Tue, 23 Aug 2005 06:51:59 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.4/8.13.4) with SMTP id j7N6oUYY010723; Tue, 23 Aug 2005 06:50:30 GMT Received: from mail-relay-3.tiscali.it (mail-relay-3.tiscali.it [213.205.33.43]) by robin.gentoo.org (8.13.4/8.13.4) with ESMTP id j7N6mkvi021121 for ; Tue, 23 Aug 2005 06:48:46 GMT Received: from default (84.222.82.234) by mail-relay-3.tiscali.it (7.2.063) id 42D763100027AD20 for gentoo-dev@lists.gentoo.org; Tue, 23 Aug 2005 08:48:24 +0200 Date: Tue, 23 Aug 2005 8:52:13 +0200 X-Mailer: InScribe Message-ID: <2ZLH1.21133GH7@gentoo.org> References: <20050821220505.4efbaff2@snowdrop.home> To: From: "Kevin F. Quinn" Subject: Re: [gentoo-dev] Fixing the TERM mess Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by robin.gentoo.org id j7N6mkvi021121 X-Archives-Salt: 6dd13d86-d68f-40a6-a2d6-b79029af3252 X-Archives-Hash: b4391edfa6541696430e4ed54c9d3ec8 On 21/8/2005 23:05:05, Ciaran McCreesh (ciaranm@gentoo.org) wrote: > Now the proposal. This isn't something that can happen immediately, but > it's something I'd like to see us working towards: > > [...] > > * De-cripple the standard xterm definition and remove restrictions from > programs which can make full use of xterm's capabilities. This bit, obviously, has to wait until at least the more common packages have been adjusted for their own TERM value. In the interim, how about creating a 'xtermstd' entry with the de-crippled definition, and altering the (presumably few) packages that supply fully-compatible xterms to use that, with a view to changing them back to 'xterm' later once the rest of the world is in line. I think it's also worth considering leaving the existing xterm entry crippled, and just accept that abuse of it is too entrenched and widespread to fix. > * Putty? Since I consider sshing from insecure systems irresponsible, I > don't know much about this one, other than that it's another dirty > liar and that said lying has caused various bugs in the past. Perhaps > someone could clarify with details of what it pretends to support and > what it really supports? I use PuTTY when I have to use Windows; it's also available for Unix. PuTTY has a configuration setting to set the terminal type string; by default this is set to "xterm" but it's easy to change to something else. This is a per-session configuration option (under Connection->Data for anyone interested), so it's easy to set it to (say) "putty" for connections to some boxes and "xterm" for others. Which means creating a "putty" terminfo definition would be workable. BTW re. colours - PuTTY seems to do 256 colours the same as a standard xterm, as far as I can tell. However that's comparing PuTTY 0.58beta with xterm-1.96 built with Cygwin on Windows from xorg-6.8.1, so it may just be they're deriving their colours from the same (Windows) palette. The only difference is that the first colour block shows up as 'X' in the cygwin xterm, but as a black block in PuTTY. The first 16 colours are black, red, green, yellow, blue, magenta, cyan and white (8 x dim then 8 x bright), followed by a 6x6x6 colour cube with black at #16, green at #46, blue at #21, red at #196 and white at #231), then a 24 step greyscale black -> white. -- gentoo-dev@gentoo.org mailing list