[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Request for inclusion of new xterm-kitty terminfo

From: Thomas Dickey
Subject: Re: Request for inclusion of new xterm-kitty terminfo
Date: Mon, 10 Sep 2018 16:12:55 -0400
User-agent: Mutt/1.5.23 (2014-03-12)

On Mon, Sep 10, 2018 at 11:28:00AM -0400, G. Branden Robinson wrote:
> [replying only to list]
> At 2018-09-10T09:32:44+0100, Nicholas Marriott wrote:
> > On Mon, Sep 10, 2018 at 07:53:24AM +0530, Kovid Goyal wrote:
> > > Sure I can dig up examples if needed, but this is a very common hack
> > > used by many terminal emulators. For example, termite uses xterm-termite
> > > gnome-terminal uses xterm-256color, konsole uses xterm-256color -- the
> > > list goes on and on. The question is why is it a problem for ncurses in
> > > the first place. Does xterm have some kind of most favored terminal
> > > status that gives it permanent ownership over all xterm-* names. And
> > > if so, IMO it is highly unfair. 
> > 
> > The solution to applications making assumptions based on a terminfo
> > entry's name rather than its capabilities is to fix those applications,
> > not to add a redundant "xterm-" prefix for terminals which are not
> > related to xterm.
> Don't modern versions of ncurses have all sorts of building blocks to
> help terminfo entry writers compose feature-based descriptions of new
> terminal types?  It seems to me that Thomas has spent quite a bit of
> effort not only making this possible, but in defining easily-digestible
> chunks to be used thus.

That isn't the issue here.  What's under discussion is one of those
non-ncurses scenarios which pretends that the actual name of the
terminal description tells you what its detailed capabilities are.

There are examples of that in the ncurses faq, such as this:


But also, the complaint seen above is rooted in the mindset mentioned here:


(applications which use ncurses's database in a shell script would use "tput"
to find information, so there's no point in providing examples of hard-coded

Earlier issues alluded to are addressed here:


as well as


And regarding licensing, recall this:


Thomas E. Dickey <address@hidden>

Attachment: signature.asc
Description: Digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]