Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.
add setfable accessors:
The problem with (read-char ext:*keyboard-input*) and unicode characters (two codes are returned for the single key pressed) is system-dependent, there is no such problem on Windows (Clisp ver 2.49 release). So it's a bug. No system info was supplied by Edgar, I just hope it's not C-64.
(#S(SYSTEM::INPUT-CHARACTER :CHAR #\CYRILLIC_SMALL_LETTER_YA :BITS 0 :FONT 0 :KEY NIL)
(#S(SYSTEM::INPUT-CHARACTER :CHAR #\CYRILLIC_SMALL_LETTER_ZE :BITS 0 :FONT 0 :KEY NIL)
(#S(SYSTEM::INPUT-CHARACTER :CHAR #\CYRILLIC_SMALL_LETTER_SHCHA :BITS 0 :FONT 0 :KEY NIL)
(#S(SYSTEM::INPUT-CHARACTER :CHAR #\CYRILLIC_SMALL_LETTER_SHA :BITS 0 :FONT 0 :KEY NIL)
Forgot to mention that Control-F1 and Control-arrows and Alt-arrows are ok too on Windows. Control/Alt are encoded in INPUT-CHARACTER-BITS.
> No system info was supplied by Edgar, I just hope it's not C-64.
Sorry, the *keyboard-input* problems appeared on Debian Lenny (Linux),
Ubuntu 10.4 (Linux) and OpenSuse Linux (exact version not known yet).
The only Windows system I have available at home is a Win2000 machine,
but I do not think that in 2010 anybody is interested in Win2k bugs.
But I know a few people who have still-working C-64 machines... :)
There are two terminal emulators in "src/stream.d", one for Windows and
one for Unix/Linux, so it looks as if the *keyboard-input* problems are
ok, so I am awaiting stream.d patches from edgar :-)
meanwhile, you can play with the old clisp screen editor from the 1990-ies in modules/ediitor
unless someone wants to work on it, it will be removed before the next release