[Top][All Lists]

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

Re: ncursesw: KEY_* and collisions with unicode chars

From: Thomas Dickey
Subject: Re: ncursesw: KEY_* and collisions with unicode chars
Date: Sun, 01 Jul 2012 11:42:13 -0400
User-agent: Mutt/1.5.18 (2008-05-17)

On Sun, Jul 01, 2012 at 04:23:59PM +0200, Felix Natter wrote:
> hello,
> a user of GTypist reported that he cannot enter a Polish character
> because it will be interpreted as backspace (KEY_BACKSPACE):
> > I noticed that it is not possible to input one of the Polish diacritic
> > letters 'c with acute' (unicode 0x107 = 263) because it interferes
> > with KEY_BACKSPACE defined in ncurses.h (0407 = 263)
> How can I tell the difference between KEY_BACKSPACE and unicode
> 0x107 (or can I teach ncursesw to return 0x8 for backspace)?
> The 'get_wch' manpage mentions KEY_CODE_YES, but IMHO this is just
> a bit that is set is a wchar_t contains a KEY_*, thus colliding with
> unicode 0x107.

A return-value of KEY_CODE_YES says that the value is a KEY_* rather
than a wchar_t (e.g., unicode).  If wget_wch returns OK, the value is
a wchar_t - there's no conflict.

Thomas E. Dickey <address@hidden>

Attachment: signature.asc
Description: Digital signature

reply via email to

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