spurious characters to stdout

[Michael Goffioul]

On 3/3/08, John W. Eaton <jwe at bevo.che.wisc.edu> wrote:
> | > The original bug report mentioned ASCII chars 30 and 31, not '1' or '0'.
> | >
> | > Michael.
> |
> | The esc sequence i get is in hex notation:
> |    1b 5b 3f 31 30 33 34 68
> | in ascii:
> |    <esc>[?1034h
>
> OK, these are the same if 31 and 30 are hex (== '1' and '0').

This explains why I couldn't find anything on the "CSI ? 34h"
control sequence....

> | The original poster told us:
> | >  <ESC>[?<US><RS>34h, where <ESC> is ASCII
> | >  27, <US> is ASCII 31, and <RS> is ASCII 30
>
> Ah, the confusion here was that 31 and 30 were decimal, which is US
> and RS in the ASCII encoding.
>
> So, who sends smm to the terminal?  I don't see that it is used
> anywhere by readline (at least not in an obvious way).

This control sequence seems to be related to enabling/disabling
meta-mode in the terminal. This might be sent by readline, when
enabling meta-key (_rl_enable_meta_key), but I can't check for
the moment.

Michael.