bug-ncurses
[Top][All Lists]
Advanced

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

Re: Question about setal in terminfo db


From: Robert Lange
Subject: Re: Question about setal in terminfo db
Date: Sat, 19 Mar 2022 22:40:04 -0400

On Sat, Mar 19, 2022 at 07:48:47PM -0400, Thomas Dickey wrote:
On Sat, Mar 19, 2022 at 05:11:37PM -0400, Robert Lange wrote:

...snip...

One other feature that I noticed that vte supported that was missing
in the terminfo entry was 'blink=\E[5m'. Not sure if there's a reason
that got left out (a lot of hate for blink in some quarters) or if it
just got missed b/c vte doesn't really document their terminal.

I overlooked it.  The git log says this was added in December 2017.

I recall some earlier comments (probably in a bug report, though
some use other forums for venting) by the developers saying that they
did not intend adding blink.

Best practice for terminal developers is to provide in their sources
a terminal description which uses the supported features (keeping
in mind that terminfo doesn't cover _all_ of the control sequences).

Presumably the developers test _their_ terminal description, and
it helps with documenting things.

In (real life) practice, a minority of terminal developers follow
best practice.  There's a lot of poor behavior in this area.

So... for these, I notice some feature while looking for something
else, or someone mentions it to me, or (probably more often than
not), it just gets ignored.

Now that I'm reminded, I can add that.  But do look at the output of

        infocmp -x xterm vte

to see a few other details where they're different.

Based on the infocmp results, I ran a few quick experiments on my vte
0.54.2 terminal and found the following additional points:

* vte supports the same Cr, Cs, E3, Se, and Ss sequences as xterm. These
  currently do not show up in the vte terminfo entry.
* vte (as vte-direct) supports the colon syntax for direct-addressed
  colors (e.g., '\E[38:2::R:G:Bm'), same as xterm. While I guess this
  syntax is "more correct", I'm not sure if it's worth changing the
  existing entry, since vte supports both colon and semicolon syntax.

--
Rob Lange



reply via email to

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