Re: [clisp-list] Weird behaviour on keyboard reading

[David P. A. <ele...@my...>]

> That's your operating system doing you a "favor" by optimizing your
> I/O for buffered throughput instead of interactivity.
> I know of no portable fix for this but
> ask your local MS-Windows wiz.

Hmm, are you sure this is the case? When I use the call (read-char
*keyboard-input*) the function waits until a key is pressed, and if such key
is shift, control, etc, it is duely detected and reported. For example:
[1]> (read-char *keyboard-input*)

#S(SYSTEM::INPUT-CHARACTER :CHAR NIL :BITS 4 :FONT 0 :KEY :SHIFT)

[2]>



So it seems the buffering issue is not it?



--David.