From: Devon S. M. <Devon@Jovi.Net> - 2006-05-17 17:17:29
|
From: "David Picon Alvarez" <ele...@my...> Date: Wed, 17 May 2006 18:59:02 +0200 Hello, I am running clisp under windows. The following code (loop (if (setq a (read-char-no-hang *keyboard-input*)) (print a))) Behaves in a counterintuitive (to me) way. The expected result would be a loop that would print any key pressed. The actual result differs. Pressing shift, or control, or such, doesn't give rise to immediate result, but later pressing return prints both the return and the former shift, control, etc. Any clues what I am doing wrong? Or suggestions on a better way to do this? 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. Peace --Devon /~\ \ / Health Care X not warfare / \ Dubya won the digital vote Kerry won the popular vote |