spurious characters to stdout

John W. Eaton jwe at bevo.che.wisc.edu
Mon Mar 3 13:11:03 CST 2008


On  3-Mar-2008, Sepp Käsbauer wrote:

| Am Montag, 3. März 2008 schrieb Michael Goffioul:
| > On Mon, Mar 3, 2008 at 4:46 PM, Sepp Käsbauer
| >
| > <cho-00047 at chiemgau-online.de> wrote:
| > >  infocmp xterm:
| > >  ...
| > >  smm=\E[?1034h
| > >  ...
| > >
| > >  If i assume that \E stands for ESC then i can confirm that smm is the
| > > same escape sequence i get in our case.
| >
| > 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').

| 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).

jwe



More information about the Bug-octave mailing list