Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: PATCH: ${(k)terminfo}
- X-seq: zsh-workers 13956
- From: Andrej Borsenkow <Andrej.Borsenkow@xxxxxxxxxxxxxx>
- To: <zsh-workers@xxxxxxxxxx>
- Subject: Re: PATCH: ${(k)terminfo}
- Date: Thu, 12 Apr 2001 11:31:11 +0400 (MSD)
- In-reply-to: <1010412012435.ZM20772@xxxxxxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
On Thu, 12 Apr 2001, Bart Schaefer wrote:
> On Apr 11, 8:30pm, Clint Adams wrote:
> }
> } This rather messily gets ${(k)terminfo} and ${(kv)terminfo} to work.
>
> Gaah. I didn't intend that you should put all those strings into the
> module source. According to "man curs_terminfo" on my system:
>
> char *boolnames, *boolcodes, *boolfnames
>
> char *numnames, *numcodes, *numfnames
>
> char *strnames, *strcodes, *strfnames
>
> These null-terminated arrays contain the capnames, the
> termcap codes, and the full C names, for each of the ter-
> minfo variables.
>
> Could we configure-check for the availability of these variables and use
> yours as fallbacks in the event that the above are not found?
>
As I understand, these variables contain names for *all* possible
capabilities, not just for the ones defined by actual terminal. So far,
there is no advantage in using them (they are missing here, I presume they
are pretty much ncurses specific, curs_terminfo manpage already smells by
ncurses). curses is pretty well documented and standard so we could just
as well take any available documentation and list all capabilities.
-andrej
Messages sorted by:
Reverse Date,
Date,
Thread,
Author