DrRacket: drop numpad Enter treatment as force-evaluation

DrRacket's interactions window tried to treat numpad Enter the same
as ctl-Return: send input to the reader, even if an S-expression is
incomplete. Since numpad Enter events were not reported as
'numpad-enter, however, the special treatment didn't take effect.

Meanwhile, it appears that some keyboard configurations report a
numpad Enter event when NumLock is on and the regular Enter key
is pressed, and that's probably not what a user wants. And
numpad Enter has never been reported differently from regular
Enter on Windows.

So, it's simpler and more consistent to just treat numpad Enter
and regular Enter the same.
This commit is contained in:
Matthew Flatt 2014-09-28 08:26:39 -06:00
parent 7d388a0795
commit a41cc0c3c0

View File

@ -955,8 +955,7 @@ TODO
(send context enable-evaluation)) (send context enable-evaluation))
(define/augment (submit-to-port? key) (define/augment (submit-to-port? key)
(or (eq? (send key get-key-code) 'numpad-enter) (or (send key get-control-down)
(send key get-control-down)
(send key get-alt-down) (send key get-alt-down)
(and prompt-position (and prompt-position
(let ([lang (drracket:language-configuration:language-settings-language user-language-settings)]) (let ([lang (drracket:language-configuration:language-settings-language user-language-settings)])