simon-git: putty (master): Simon Tatham

[Commits to Tartarus hosted VCS]

TL;DR:
  97a10212 Fix handling of Return and keypad Enter.

Repository:     https://git.tartarus.org/simon/putty.git
On the web:     https://git.tartarus.org/?p=simon/putty.git
Branch updated: master
Committer:      Simon Tatham <anakin at pobox.com>
Date:           2019-04-15 20:48:01

commit 97a1021202d39e8a19832e64a8a92f923b68a56a
web diff https://git.tartarus.org/?p=simon/putty.git;a=commitdiff;h=97a1021202d39e8a19832e64a8a92f923b68a56a;hp=56198afb5c1f5e5ce606f45c6e214073c75c9901
Author: Simon Tatham <anakin at pobox.com>
Date:   Mon Apr 15 20:43:10 2019 +0100

    Fix handling of Return and keypad Enter.
    
    The recent rewriting in both the GTK and Windows keyboard handlers
    left the keypad 'Enter' key in a bad state, when no override is
    enabled that causes it to generate an escape sequence.
    
    On Windows, a series of fallbacks was causing it to generate \r
    regardless of configuration, whereas in Telnet mode it should default
    to generating the special Telnet new-line sequence, and in response to
    ESC[20h (enabling term->cr_lf_return) it should generate \r\n.
    
    On GTK, it wasn't generating anything _at all_, and also, I can't see
    any evidence that the GTK keyboard handler had ever remembered to
    implement the cr_lf_return mode.
    
    Now Keypad Enter in non-escape-sequence mode should behave just like
    Return, on both platforms.

 unix/gtkwin.c    | 44 +++++++++++++++++++++++++++++++++++++-------
 windows/window.c | 34 +++++++++++++++++++++++-----------
 2 files changed, 60 insertions(+), 18 deletions(-)