Hey, nobody ever replied but the answer is, don't use Microsoft telnet
client with cygwin expect.
Install cygwin telnet client ( NOT installed by default, heaven alone knows
why when they have a gazillion other things installed by default that will
only be useful to 0.000
]
Sent: Monday, March 01, 2004 7:37 PM
To: Wolmarans, Brett; '[EMAIL PROTECTED]'
Subject: Re: invalid spawn id (4)
At 07:33 PM 3/1/2004, you wrote:
>Hey, nobody ever replied but the answer is, don't use Microsoft telnet
>client with cygwin expect.
>
>Install cygwin te
: Wolmarans, Brett
Subject: RE: invalid spawn id (4)
Brett,
Humor and indignation aside, it might be a useful feature to have
"installation profiles" for setup based on intended usage. That way,
instead of having to wade through all the packages (on a too-small screen,
no less [an inside j
]
Sent: Tuesday, March 02, 2004 1:01 PM
To: Wolmarans, Brett; 'Cygwin List'; Wolmarans, Brett
Subject: RE: invalid spawn id (4)
Brett, I understood your point. You clearly didn't catch mine though, I
guess because it was shrouded in humor. I'll be more plain.
The a
: Wolmarans, Brett
Cc: [EMAIL PROTECTED]
Subject: RE: invalid spawn id (4)
Brett,
First off, please configure your mailer to not quote raw e-mail addresses
in your replies -- the spam harvesters have it too easy already.
And I actually was not joking -- Cygwin setup, just like Cygwin itself, is
Anybody know how to resolve or work around this bug in expect: invalid spawn
id (4) the first time I try to something incredibly common such as use
expect to automate a telnet session. I could not find any references to
this in the faq or archives, found one hit on google but no solution.
cygwin
6 matches
Mail list logo
