[no subject]

[RMS@MIT-AI]

    RG@MIT-AI (Sent by RG0@MIT-AI) 01/11/79 21:50:23
      HACKING THE NEW WINDOW STUFF IN EINE, I MANAGED TO GET IT INTO A
    STATE WHERE ALL PROCESSES WERE BLOCKED "PERMANENTLY".  I THINK I DID
    IT BY FROBBING OTHER MOUSE BUTTONS WHILE I WAS TRANSLATING AN EDITOR WINDOW.
     MAYBE THE SCHEDULER SHOULD SENSE CALL NOT BEING HANDLED AN INITIATE A
    SUPER-BREAKPOINT SO YOU COULD GET A CHANCE TO SEE WHY THINGS ARE SO HUNG UP.

The scheduler does check for call by doing (KBD-CHAR-AVAILABLE T).
I too have seen this not work, but I don't know why.
Maybe it means that a CALL can't be seen if there is an
unread character in front of it.
If so, we probably need real keyboard interrupts
to fix this properly.