Date:	Wed, 16 Aug 2000 15:08:04 +0200
From:	"Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender:	halo1 AT zahav DOT net DOT il
To:	jeffw AT darwin DOT sfbr DOT org
Message-Id:	<2593-Wed16Aug2000150803+0300-eliz@is.elta.co.il>
X-Mailer:	Emacs 20.6 (via feedmail 8.2.emacs20_6 I) and Blat ver 1.8.5b
CC:	djgpp AT delorie DOT com
In-reply-to:	<200008160937.EAA00158@darwin.sfbr.org> (message from Jeff T
	Williams on Wed, 16 Aug 2000 04:43:03 -0600)
Subject:	Re: bash 2.03 'history' gives \r\n terminated lines
References:	<200008160937 DOT EAA00158 AT darwin DOT sfbr DOT org>
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> From: Jeff T Williams <jeffw AT darwin DOT sfbr DOT org>
> Date: Wed, 16 Aug 2000 04:43:03 -0600
> 
> With the DJGPP port of bash 2.03 I note that
> 'history' terminates each output line with '\r\n' instead of just '\n'.

Yes, that's how the DJGPP port of the Readline library works: it does
file I/O in text mode.

> Is this the expected behavior?

It was a deliberate decision to leave the I/O at text mode, yes.

Personally, I'm not happy about it.  The redirection to a Unix-style
file is a nuisance, but I'm concerned about the more serious case
where a non-printable character such as Ctrl-Z sneaks into the history
file due to some peculiar set of commands.

At the time, I submitted patches to Readline to use binary I/O for
history files, but those patches did not make it into the current
sources.  Since the problematic cases are marginal, I didn't protest
too vociferously.

- Raw text -