public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaranm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Fixing the TERM mess
Date: Tue, 23 Aug 2005 22:29:11 +0100	[thread overview]
Message-ID: <20050823222911.6891f563@snowdrop.home> (raw)
In-Reply-To: <1124830648.12024.95.camel@cocagne.max-t.internal>

[-- Attachment #1: Type: text/plain, Size: 1354 bytes --]

On Tue, 23 Aug 2005 16:57:28 -0400 Olivier Crete <tester@gentoo.org>
wrote:
| As a gnome-terminal user, I've never had problems with anything that
| tried to use advanced xterm crap... probably because no uses them. If
| you want X stuff, just use a real X application (like gvim...). I'm
| strictly opposed to crippling my terminal use in the most common cases
| (such a logging into a non-Gentoo system) for one or two legacy
| applications.

Ok, to put this into perspective: the next major release of vim will
almost certainly not work on anything that calls itself an xterm unless
it really is an xterm. You will likely encounter a hard locked terminal
that you can't unlock. The latest ncurses release will also break
various things (irssi comes to mind) on Gnome Terminal.

Crippling xterm is no longer considered a suitable workaround. 

| In the era of massive sshing, we have to forget terminfo and new
| terminal types. We should understand xterm to mean a basic x terminal
| and not the application from X.org. 

Uh, no, a basic x terminal would be TERM=vt100. If an application
claims TERM=xterm, it is expected to support full xterm capabilities.

-- 
Ciaran McCreesh : Gentoo Developer (Vim, Shell tools, Fluxbox, Cron)
Mail            : ciaranm at gentoo.org
Web             : http://dev.gentoo.org/~ciaranm


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-08-23 21:31 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-21 21:05 [gentoo-dev] Fixing the TERM mess Ciaran McCreesh
2005-08-21 22:00 ` Henrik Brix Andersen
2005-08-21 22:13   ` Ciaran McCreesh
2005-08-21 22:41     ` Henrik Brix Andersen
2005-08-21 22:43     ` [gentoo-dev] " Dan Meltzer
2005-08-21 23:08       ` Ciaran McCreesh
2005-08-22  0:21         ` Renat Lumpau
2005-08-22  7:18           ` Tavis Ormandy
2005-08-22  7:46             ` Tavis Ormandy
     [not found]           ` <605B5D3B660EFCD90AD3B473@10.0.0.1>
     [not found]             ` <7C3236ADA8D6B69461A1FF62@10.0.0.1>
2005-08-22 12:44               ` Dan Meltzer
2005-08-29 10:44         ` Francesco R
2005-08-22 12:51 ` [gentoo-dev] " Mike Frysinger
2005-08-23  6:52 ` Kevin F. Quinn
2005-08-23 20:27   ` Ciaran McCreesh
2005-08-23 20:57     ` Olivier Crete
2005-08-23 21:29       ` Ciaran McCreesh [this message]
2005-08-24  0:01       ` Georgi Georgiev
2005-08-23 23:56 ` [gentoo-dev] " Sven Köhler
2005-08-24 11:55   ` Martin Schlemmer
2005-08-24  0:10 ` Sven Köhler
2005-08-24 12:07   ` Ciaran McCreesh
2005-08-29  7:28     ` ivan vadovič
2005-08-29 14:53       ` Ciaran McCreesh
2005-09-08 16:50         ` ivan
2005-09-08 16:59           ` Ciaran McCreesh
2005-09-01 18:27 ` Joe Wells
2005-09-06 19:19   ` Jan Kundrát
2005-09-07  8:31     ` YoYo Siska
2005-09-09 16:24     ` Joe Wells (reverse mailbox letters only for non-public replies)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050823222911.6891f563@snowdrop.home \
    --to=ciaranm@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox