Re: LW 8.1 keyboard issue

Sorry, this change was missed from the release notes.  The Windows platform
now recognizes KP-Enter as a distinct key like the other platforms have done
for a while, but we didn't add default bindings for the Listener and Echo
Area.

These bindings might help:

(editor:bind-key "Confirm Parse" "KP-Enter" :mode "Echo Area")
(editor:bind-key "Execute or Insert Newline or Yank from Previous Prompt" "KP-Enter"
                 :mode "Execute")

-- 
Martin Simmons
LispWorks Ltd
http://www.lispworks.com/



>>>>> On Sun, 9 Mar 2025 13:49:39 -0400, Paul Werkowski (as pw at snoopy dot qozzy dot com) said:
> 
> The original issue was not about keyboards w/wo key pads. I was that 
> Listener handles kp enter differently from prior versions. It appears 
> that what is entered after the CL-USER > prompt is saved in some buffer 
> (including the #\newline character) until the other Enter key is 
> pressed. Here is an example:
> 
> 
> CL-USER 9 > (* 2 2)         | KP enter pressed after ")"
> 4                                         | "4" does not appear yet
> Error while reading: Unmatched right parenthesis. | nor this
> 
> CL-USER 10 > ;
> ;
> ;
> )
> ^
> The "4"  , error msg and second prompt were not printed until after 
> pressing KB Enter
> indicated by ^.
> 
> I've been using LW since it was formerly called HCL. This is new and not 
> mentioned in the release notes. Perhaps it works better in UK?
> 
> 
> 
> _______________________________________________
> Lisp Hug - the mailing list for LispWorks users
> [email protected]
> http://www.lispworks.com/support/lisp-hug.html
> 

_______________________________________________
Lisp Hug - the mailing list for LispWorks users
[email protected]
http://www.lispworks.com/support/lisp-hug.html