Message-Id: <199903141552.JAA22580@darwin.sfbr.org>
Date: Sun, 14 Mar 1999 09:52:36 -0600 (CST)
From: Jeff Williams <jeffw AT darwin DOT sfbr DOT org>
Subject: Re: bash 2.03 beta binary
To: djgpp AT delorie DOT com
Cc: snowball3 AT usa DOT net
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: IE74uDrHfxNJjmXW35yymg==
X-Mailer: dtmail 1.2.0 CDE Version 1.2 SunOS 5.6 sun4m sparc 
Reply-To: djgpp AT delorie DOT com

-: Jeff Williams <jeffw AT darwin DOT sfbr DOT org> wrote:
-: 
-: >The only difference I see so far is that the 2.03 bash does not read the
-: >_inputrc file for readline, and therefore starts in emacs editing-mode
-: >rather than my preferred vi editing-mode.  I can `source' the _inputrc

-: Mark E.: snowball3 AT usa DOT net
-:
-: the updated Bash. Until I can update the site with a new binary with a fix
-: for your problem, you can workaround it by defining the environment
-: variable INPUTRC to '~/_inputrc'  before starting Bash.

OK, when I set INPUTRC=~/_inputrc the _inputrc file is found on startup,
but bash/readline then hangs with the following message:

readline: ~/_inputrc: line 50: unknown parser directive
readline: ~/_inputrc: line 52: unknown parser directive

At this point I can enter/edit text on the command line, but Enter, Ctrl-C,
Break, etc, are not recognized and the only way out is Ctrl-Alt-Del.

Note: my _inputrc file has only 48 lines!  On the outside chance that
readline's line numbers are off by some small constant, the error
messages *might* be referring to the $endif directive (lines 46 and 48)
in my file.

j