Date: Mon, 10 May 1999 09:32:24 +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: v2.03: wrapping up
In-Reply-To: <199905091641.QAA48022@out1.ibm.net>
Message-ID: <Pine.SUN.3.91.990510093150.2882A-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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
Precedence: bulk


On Sun, 9 May 1999, Mark E. wrote:

> It would also be nice if we could find a way to let '~'  be a valid first 
> character of a default string since under the current scheme a default 
> string with special meaning to Bash like '~/_inputrc' is disallowed.

`~' is only special in a file name which begins with "/dev/env";
otherwise it's just a normal character.  So how does the code I posted
disallow "~/_inputrc"?