Date: Mon, 15 Feb 1999 10:02:21 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: "Mark E." <snowball3 AT usa DOT net>
cc: djgpp-workers AT delorie DOT com
Subject: Re: new Bash 2.02.1 test version available
In-Reply-To: <199902141710.RAA12116@out2.ibm.net>
Message-ID: <Pine.SUN.3.91.990215100140.10128A-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com


On Sun, 14 Feb 1999, Mark E. wrote:

> >   - .bash_history tends to get spurious ^M characters appended to some of 
> >     the saved commands.
> 
> Yep, I've noticed this. Unfortunately, I noticed it well before mixed EOL 
> fix so I still don't where to look until I or somebody else can find a 
> consistent way to make the bug happen.

This does the trick for me:

     rm -f /.bash_history
     bash
     bash-2.02$ exit
     bash
     bash-2.02$ exit   <- press <up-arrow> to get this line
     bash
     bash-2.02$ ^M     <- press <up-arrow> again here, and you see ^M

(The first line might need to be changed if you keep your
.bash_history somewhere else.)