Re: [Chicken-users] chicken 4.8.0.5 on cygwin - stty ECHOPRT

2014-04-03 Thread Alex Shinn
On Mon, Mar 31, 2014 at 3:15 AM, Claude Marinier claudem...@gmail.comwrote: On Sun, 30 Mar 2014, Claude Marinier wrote: I just built chicken 4.8.0.5 on MS Windows Vista with a somewhat recent cygwin. The installation process went well but csi could not find parley. Turns out parley needs

Re: [Chicken-users] chicken 4.8.0.5 on cygwin - stty ECHOPRT

2014-04-03 Thread John Cowan
Alex Shinn scripsit: Yes please, I usually only skim subjects :) Ah, then you missed my argument. I'll conditionally compile out ECHOPRT. ECHOPRT should be removed unconditionally. It is not Posix and is only useful on hard-copy terminals, which are non-existent these days. -- John Cowan

Re: [Chicken-users] chicken 4.8.0.5 on cygwin - stty ECHOPRT

2014-04-01 Thread Claude Marinier
On Sun, 30 Mar 2014, Claude Marinier wrote: On Sun, 30 Mar 2014, Claude Marinier wrote: I just built chicken 4.8.0.5 on MS Windows Vista with a somewhat recent cygwin. The installation process went well but csi could not find parley. Turns out parley needs stty which did not compile because

Re: [Chicken-users] chicken 4.8.0.5 on cygwin - stty ECHOPRT

2014-03-30 Thread Claude Marinier
On Sun, 30 Mar 2014, Claude Marinier wrote: I just built chicken 4.8.0.5 on MS Windows Vista with a somewhat recent cygwin. The installation process went well but csi could not find parley. Turns out parley needs stty which did not compile because it cannot find the symbol ECHOPRT. I removed

Re: [Chicken-users] chicken 4.8.0.5 on cygwin - stty ECHOPRT

2014-03-30 Thread John Cowan
Claude Marinier scripsit: I neglected to mention that removing references to ECHOPRT in stty is not a proper solution; it just allowed me to use Chicken on MS Windows. In fact, ECHOPRT should simply be flushed. It is not part of Posix, and is in fact useful only on long-obsolete printing