zsh-workers
 help / color / mirror / code / Atom feed
From: Andrej Borsenkow <Andrej.Borsenkow@mow.siemens.ru>
To: <zsh-workers@sunsite.dk>
Subject: Re: PATCH: use curses library capability inventory and hope it's terminfo
Date: Thu, 12 Apr 2001 11:32:38 +0400 (MSD)	[thread overview]
Message-ID: <Pine.SV4.4.33.0104121131200.23702-100000@itsrm2.mow.siemens.ru> (raw)
In-Reply-To: <1010412032348.ZM20888@candle.brasslantern.com>

On Thu, 12 Apr 2001, Bart Schaefer wrote:

> On Apr 11, 10:44pm, Clint Adams wrote:
> } Subject: PATCH: use curses library capability inventory and hope it's term
> }
> } >        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.
> }
> } Note that it says "termcap" codes.  The great thing is that on Solaris,
> } it will actually contain terminfo capability names (which is what we
> } want), but under ncurses, it will contain termcap capability names.
>
> ??  The `names' arrays are supposed to contain the terminfo names, and
> the `codes' arrays the termcap codes.  Do you mean that the two will be
> the same under ncurses?
>

Yes. Cf. infocmp command that lists short and long terminfo names and
termcap names.

-andrej


  parent reply	other threads:[~2001-04-12  7:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-12  0:30 PATCH: ${(k)terminfo} Clint Adams
2001-04-12  1:24 ` Bart Schaefer
2001-04-12  2:44   ` PATCH: use curses library capability inventory and hope it's terminfo Clint Adams
2001-04-12  3:23     ` Bart Schaefer
2001-04-12  4:05       ` PATCH: correct idiocy Clint Adams
2001-04-12  7:32       ` Andrej Borsenkow [this message]
2001-04-12  7:31   ` PATCH: ${(k)terminfo} Andrej Borsenkow

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=Pine.SV4.4.33.0104121131200.23702-100000@itsrm2.mow.siemens.ru \
    --to=andrej.borsenkow@mow.siemens.ru \
    --cc=zsh-workers@sunsite.dk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).