According to the man page, if you omit the asyncmap completely, it
requests escaping of _all_ control characters, ie, 0xffffffff


On Tue, 26 May 1998, Ken Hornstein wrote:

> >Oh, somehow I misunderstood your first message a bit. I admit I am a bit
> >astonished, but that option does the trick. it would be nice if you could
> >describe shortly what this "asyncmap" does. According to the man it
> >escapes control sequences that can't be transferred over the line. But
> >that starts for 0x00 with a value of 0x00000001 and so on. Does 0 stand
> >for "All characters can be transferred"? If so, why would I need to set
> >the option at all?
> 
> It's a bitmask for the first 32 characters.  A value of 0x00000001 means
> "escape ASCII 0x01", a value of 0x00000002 means "escape ASCII 0x02",
> a value of 0x00000003 means "escape ASCII 0x01 and 0x02", etc etc.  A
> value of 0x00 means "don't escape any characters".
> 
> As for why you would need this option at all ... I'm not quite sure,
> actually.  I believe that if this isn't specified at all, you don't
> negotiate an asyncmap and both sides are expected to escape all
> characters.  Do you know what's on the remote end?
> 
> --Ken
> 

-----------------------------------------------------------------------------
| Paul Goyette      | Public Key fingerprint:    | E-mail addresses:        |
| Network Engineer  |   0E 40 D2 FC 2A 13 74 A0  |  paul@whooppee.com       |
| and kernel hacker |   E4 69 D5 BE 65 E4 56 C6  |  paul.goyette@ascend.com |
-----------------------------------------------------------------------------