Re: Maintaining expect (the broken pipe errors)

2017-04-10 Thread Dan Kegel
On Mon, Apr 10, 2017 at 11:43 AM, Marco Atzeri wrote: > http://wiki.tcl.tk/201 > > name > Expect > website > http://expect.sf.net > website > http://expect.nist.gov Accurate, but it's still a bit surprising that expect's source repo is unlike the rest of tcl's

Re: Maintaining expect (the broken pipe errors)

2017-04-10 Thread Marco Atzeri
On 10/04/2017 19:03, Dan Kegel wrote: On Mon, Apr 10, 2017 at 8:58 AM, Brian Inglis wrote: A Cygwin package is available for expect and the repo is on SF at: https://sourceforge.net/p/expect/code/ which gives the CVSROOT:

Re: Maintaining expect (the broken pipe errors)

2017-04-10 Thread Dan Kegel
On Mon, Apr 10, 2017 at 8:58 AM, Brian Inglis wrote: > A Cygwin package is available for expect and the repo is on SF at: > https://sourceforge.net/p/expect/code/ > which gives the CVSROOT: >

Re: Maintaining expect (the broken pipe errors)

2017-04-10 Thread Brian Inglis
On 2017-04-09 17:06, Daniel Santos wrote: > I should probably import this onto my github account. There doesn't > appear to be an actual repository for expect at the moment. There are > many terrible coding practices employed, potential use of > uninitialized locals, etc. I'm going to do some

Re: Maintaining expect (the broken pipe errors)

2017-04-09 Thread Václav Haisman
On 10 April 2017 at 01:06, Daniel Santos wrote: > I should probably import this onto my github account. There doesn't appear > to be an actual repository for expect at the moment. There are many > terrible coding practices employed, potential use of uninitialized

Maintaining expect (the broken pipe errors)

2017-04-09 Thread Daniel Santos
I should probably import this onto my github account. There doesn't appear to be an actual repository for expect at the moment. There are many terrible coding practices employed, potential use of uninitialized locals, etc. I'm going to do some basic cleanup before I dig back into trying to