From: Ian Chapman <ichapman AT nortelnetworks DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Bash 2.03
Date: Tue, 28 Mar 2000 12:14:06 -0500
Organization: Nortel
Lines: 35
Message-ID: <38E0E85E.80CD1C1A@nortelnetworks.com>
References: <38DB6D8A DOT B4304246 AT nortelnetworks DOT com>
NNTP-Posting-Host: bcarib90.ca.nortel.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 4.7 [en] (Win95; U)
X-Accept-Language: en
To: djgpp AT Delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

I fixed it by copying the 2.03 _inputrc file into djgpp in place of the
one from 1.47. 

		Regards Ian.

Ian Chapman wrote:
> 
> Hi,
>         I'm in the process of updating my gnu software to the latest release
> level.  Rather than junking all the old release on my drive f: I'm
> putting all the latest on drive d:, that way I'm never down.
> 
>         I've got Bash 1.47 on drive f: and I've been using it for some time
> with good results.  It's better than dos.
> 
>         I've just unzipped the new bash 2.03 (plus the new gnu ports) onto my
> drive d:.  I've also copied my existing _bash start up files into
> d:/djgpp.  I invoke Bash 2.03 using the same process as previous but
> changing my dos bat files from f: to d: and my _bashrc file from f: to
> d: both location and contents as appropriate.  It starts up fine but
> whenever I hit the key 'e' it prints on the screen:-
> 
> "running _bashrc"
> and if I hit return it does indeed re-run  the _bashrc file.
> 
>         All the  commands without an "e" seem fine I had to change some dot.inf
> to dot.info to use them.
> 
>         I must be doing something silly.  I'll re-read the readme files, if any
> of you have any ideas please reply.
> 
>                 Regards Ian.
> PS
>         I put a unix version of bash 2.03 on a unix box at work (I ran make)
> without difficulties and used my _bashrc file there okay.