Date: Mon, 10 May 1999 11:40:43 +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>, djgpp-workers AT delorie DOT com
Subject: RE: v2.03: wrapping up
In-Reply-To: <Pine.SUN.3.91.990510093150.2882A-100000@is>
Message-ID: <Pine.SUN.3.91.990510113243.10461B-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 Mon, 10 May 1999, I wrote:

> 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.

If you want to use ~/foo or ~user/foo in the default value, simply use 
/dev/env/HOME instead, like this:

     inputrc_name = "/dev/env/DJDIR/etc~/dev/env/HOME~/_inputrc"

Since there's only one user in DJGPP anyway, both ~/ and ~user/ map to 
the value of $HOME.

As to your suggestion to use a colon `:', it is not a good idea, since 
colons are special in Makefile's.  I actually thought about using the 
colons before the tilde was suggested, so I tested it: Make got utterly 
confused when /dev/env/FOO:foo was used in some contexts.

Thanks for the feedback.  I incorporated the rest of your suggestions.