From:	jmichel AT schur DOT institut DOT math DOT jussieu DOT fr (Jean Michel)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Bug in djgpp libc
Date:	1 Jan 2001 21:20:59 +0100
Organization:	A poorly-installed InterNetNews site
Lines:	18
Message-ID:	<92qorb$1c4$1@schur.institut.math.jussieu.fr>
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 1010101162145 DOT 9706D-100000 AT is> <92qb0f$17r$1 AT schur DOT institut DOT math DOT jussieu DOT fr> <2561-Mon01Jan2001204906+0200-eliz AT is DOT elta DOT co DOT il>
NNTP-Posting-Host:	schur.institut.math.jussieu.fr
Mime-Version:	1.0
X-Trace:	vishnu.jussieu.fr 978380077 15763 134.157.13.71 (1 Jan 2001 20:14:37 GMT)
X-Complaints-To:	Newsmaster AT jussieu DOT fr.
NNTP-Posting-Date:	1 Jan 2001 20:14:37 GMT
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

>I'd still like to know if the suggestions I made help you solve the
>problem, and if not, why.

The suggestions  you made imply put  some ifdefs in the  ruby source for
this particular port. I  am not a ruby developer, but  I get the feeling
this port  is not very  popular anyway (Cygwin  one is more  popular) so
people may  just stop supporting the  djgpp port if too  many ifdefs are
needed...

>
>One other possibility is to use the DJGPP termios emulation, which
>modifies the console I/O so that ^Z is no longer a problem.  If ruby
>is an interactive program coming from Unix, it probably tries to use
>termios anyway; perhaps the DJGPP port disables that for some
>(histerical?)  reasons, in which case all you need to do is remove the
>disabling code.

Thanks for the suggestion. I will look into that.

- Raw text -