simon-git: putty (master): Simon Tatham

[Commits to Tartarus CVS repository.]

TL;DR:
  2ce0b68 Loop over all _supported_, not just configured, SSH tty modes.
  2a73676 Support frontend_is_utf8() in all front ends.
  dcf4466 Send the IUTF8 terminal mode in SSH "pty-req"s.

Repository:     git://git.tartarus.org/simon/putty.git
On the web:     http://tartarus.org/~simon-git/gitweb/?p=putty.git
Branch updated: master
Committer:      Simon Tatham <anakin at pobox.com>
Date:           2016-05-03 11:15:56

commit 2ce0b680cf7bcc1a2a4529fd51f0f972a4fad18e
web diff http://tartarus.org/~simon-git/gitweb/?p=putty.git;a=commitdiff;h=2ce0b680cf7bcc1a2a4529fd51f0f972a4fad18e;hp=8a2797cf0f32de5f2814609a3a64dd4c7dd63457
Author: Simon Tatham <anakin at pobox.com>
Date:   Mon May 2 13:51:28 2016 +0100

    Loop over all _supported_, not just configured, SSH tty modes.
    
    Previously, the code that marshalled tty settings into the "pty-req"
    request was iterating through the subkeys stored in ssh->conf, meaning
    that if a session had been saved before we gained support for a
    particular tty mode, the iteration wouldn't visit that mode at all and
    hence wouldn't send even the default setting for it.
    
    Now we iterate over the array of known mode identifiers in
    ssh_ttymodes[] and look each one up in ssh->conf, rather than vice
    versa. This means that when we add support for a new tty mode with a
    nontrivial policy for choosing its default state, we should start
    using the default handler immediately, rather than bizarrely waiting
    for users to save a session after the change.

 ssh.c |   50 +++++++++++++++++++++++++++++---------------------
 1 file changed, 29 insertions(+), 21 deletions(-)

commit 2a73676490570520e6dbb3bc856b0710a645c2bd
web diff http://tartarus.org/~simon-git/gitweb/?p=putty.git;a=commitdiff;h=2a73676490570520e6dbb3bc856b0710a645c2bd;hp=2ce0b680cf7bcc1a2a4529fd51f0f972a4fad18e
Author: Simon Tatham <anakin at pobox.com>
Date:   Tue May 3 08:43:09 2016 +0100

    Support frontend_is_utf8() in all front ends.
    
    Previously only Unix front ends bothered to include it, on the basis
    that only the pty backend needed it (to set IUTF8 in the pty). We're
    about to need it everywhere else too.

 fuzzterm.c       |    1 +
 windows/window.c |    5 +++++
 2 files changed, 6 insertions(+)

commit dcf44663057ec4df3581f8fd2a31c65a98e6988a
web diff http://tartarus.org/~simon-git/gitweb/?p=putty.git;a=commitdiff;h=dcf44663057ec4df3581f8fd2a31c65a98e6988a;hp=2a73676490570520e6dbb3bc856b0710a645c2bd
Author: Simon Tatham <anakin at pobox.com>
Date:   Tue May 3 08:43:50 2016 +0100

    Send the IUTF8 terminal mode in SSH "pty-req"s.
    
    An opcode for this was recently published in
    https://tools.ietf.org/html/draft-sgtatham-secsh-iutf8-00 .
    
    The default setting is conditional on frontend_is_utf8(), which is
    consistent with the pty back end's policy for setting the same flag
    locally. Of course, users can override the setting either way in the
    GUI configurer, the same as all other tty modes.

 settings.c |   10 +++++-----
 ssh.c      |    1 +
 terminal.c |    2 ++
 3 files changed, 8 insertions(+), 5 deletions(-)