simon-git: putty (main): Simon Tatham

[Commits to Tartarus hosted VCS]

TL;DR:
  de66b031 Allow terminating OSC sequences during setup.

Repository:     https://git.tartarus.org/simon/putty.git
On the web:     https://git.tartarus.org/?p=simon/putty.git
Branch updated: main
Committer:      Simon Tatham <anakin at pobox.com>
Date:           2022-05-11 21:15:23

commit de66b0313a23d04312235cbf2054b882f554d21f
web diff https://git.tartarus.org/?p=simon/putty.git;a=commitdiff;h=de66b0313a23d04312235cbf2054b882f554d21f;hp=e9de549e7e0b4f31683f8815e1b402a2f63e0fa3
Author: Simon Tatham <anakin at pobox.com>
Date:   Wed May 11 20:07:31 2022 +0100

    Allow terminating OSC sequences during setup.
    
    A user reports that the xterm OSC 112 sequence (reset cursor colour)
    is sometimes sent as simply OSC 112 BEL, rather than OSC 112 ; BEL.
    When xterm parses this, the BEL still acts as an OSC terminator, even
    though it appears before the separating semicolon that shifts into the
    'absorb the notional command string' state.
    
    PuTTY doesn't support that sequence at all. But currently, the way it
    doesn't support it is by treating the BEL completely normally, so that
    you get an annoying beep when a client application sends that
    abbreviated sequence.
    
    Now we recognise all the OSC terminator sequences even in the OSC
    setup termstates, as well as the final OSC_STRING state. That goes
    equally for BEL, ST in the form of ESC \, ST in the form of
    single-byte 0x9C, and ST in the UTF-8 encoding.

 terminal/terminal.c | 41 ++++++++++++++++++++++++++++++++++++++++-
 1 file changed, 40 insertions(+), 1 deletion(-)