From: Ciaran McCreesh <ciaranm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Fixing the TERM mess
Date: Sun, 21 Aug 2005 23:13:56 +0100 [thread overview]
Message-ID: <20050821231356.050432ce@snowdrop.home> (raw)
In-Reply-To: <1124661626.13706.13.camel@sponge.fungus>
[-- Attachment #1: Type: text/plain, Size: 1824 bytes --]
On Mon, 22 Aug 2005 00:00:26 +0200 Henrik Brix Andersen
<brix@gentoo.org> wrote:
| > * Install, either with the terminal (as is done by rxvt-unicode
| > currently), or as part of ncurses, proper terminfo definitions for
| > these terminals.
|
| One could argue for both solutions here: it would make sense to
| install it along with the offending terminal, since this is where we
| change the value of the $TERM variable.
The problem with this is that non-X boxes will be missing the terminfo
descriptions.
| Perhaps we should just once-and-for-all submit a patch to ncurses
| which includes these new terminfo definitions? We will then patch our
| foo-terminal ebuilds to set a proper value of $TERM. Then when
| upstream (hopefully) decides to change their $TERM value to something
| sane, ncurses will already have the support, and we can remove the
| local patch along with the version bump of foo-terminal.
The problem with this is that some terminals gain new capabilities
fairly regularly. One example is rxvt-unicode, which is still putting
out regular releases.
A third possibility is to split out the terminfo db from ncurses. This
will let us do frequent updates if necessary. It may also help the
embedded people -- we could add a USE=minimal which only installs
'common' definitions and leaves out support for obscure 1950s line
printers. There may be a gaping hole in this idea. I haven't thought it
through much...
| > * Include TERM stuff in policy so that the problem doesn't crop up
| > again a few months later.
|
| I'm not sure what you mean by "policy"?
That thing we don't have yet.
--
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 --]
next prev parent reply other threads:[~2005-08-21 22:17 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 [this message]
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
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=20050821231356.050432ce@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