Date: Tue, 24 Jul 2001 13:43:29 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: "Mark E." <snowball3 AT bigfoot DOT com>
cc: djgpp-workers AT delorie DOT com
Subject: Re: extended keys support
In-Reply-To: <3B5C8550.21789.243885@localhost>
Message-ID: <Pine.SUN.3.91.1010724134125.1341M-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Mon, 23 Jul 2001, Mark E. wrote:

> + static const unsigned char *
> + ext_key_string_table[] =
> + {
> +   "\e[[A",  /* 0x3B: F1 */
> +   "\e[[B",  /* 0x3C: F2 */
> +   "\e[[C",  /* 0x3D: F3 */
> +   "\e[[D",  /* 0x3E: F4 */

Shouldn't this table be available to other parts of the library, via
some function that looks up a string given a key?  I'd imagine tgetstr
from termcap would like to know that, right?