Date:	Mon, 26 Jul 1999 09:29:45 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	"Mark E." <snowball3 AT bigfoot DOT com>
cc:	djgpp-workers AT delorie DOT com
Subject:	Re: Current diffs against Readline 4.0
In-Reply-To:	<199907251528.PAA41436@out4.ibm.net>
Message-ID:	<Pine.SUN.3.91.990726092924.27650C-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Sun, 25 Jul 1999, Mark E. wrote:

> You're right. Turns out Bash comes with GNU Termcap, but the 
> standalone Readline package doesn't. But we could use GNU 
> Termcap with Readline, since they're both under the same license. 

This means that people will need to install Termcap to build GDB and
other packages which don't come with GNU Termcap in the box.  And
there's no Termcap on SimTel.NET, sigh...

I'm unsure what would be the best way of handling this.  Do we agree
to add to libc.a in the next DJGPP release some minimal termcap
functionality that would work with (the improved) termios?  If we do,
then it's probably not wise to submit changes to the Readline
maintainer that would be withdrawn in a few months.

But if termcap functionality will not be in libc soon, I'd probably
opt for leaving some of the DJGPP-related changes inside Readline,
perhaps conditioned on HAVE_TERMCAP or something.

> As a test, I typed in 'test' then ctrl-a at the Bash command line. I found 
> the ctrl-a unescaped in the history file. If we want to able to store a CR 
> not with a LF, then the stripping will need to be done as you suggest.

I was afraid of such cases.  I think it is better to strip CRs
explicitly in the code, rather than rely on library functions; I don't
like to surprise the user and/or have subtle misfeatures that trigger
FAQs.

- Raw text -