From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: Re: PATCH: termcap special param
Date: Sat, 14 Apr 2001 01:41:18 +0000 [thread overview]
Message-ID: <1010414014118.ZM2313@candle.brasslantern.com> (raw)
In-Reply-To: <20010413194255.A31289@dman.com>
On Apr 13, 7:42pm, Clint Adams wrote:
} Subject: PATCH: termcap special param
}
} Is there a configure test we can use instead of the NCURSES_VERSION
} check?
There's no mention of NCURSES_VERSION anywhere in this patch ... what
check do you mean?
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2001-04-14 1:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-13 23:42 Clint Adams
2001-04-14 1:41 ` Bart Schaefer [this message]
2001-04-14 3:22 ` Clint Adams
2001-04-14 5:15 ` 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=1010414014118.ZM2313@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--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).