From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: setting INFOPATH
Date: Sat, 08 Jan 2000 10:39:51 +0200
Organization: NetVision Israel	
Lines: 31
Message-ID: <3876F7D7.7E149E88@is.elta.co.il>
References: <200001071829 DOT MAA02034 AT darwin DOT sfbr DOT org>
NNTP-Posting-Host: ras1-p79.rvt.netvision.net.il
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Trace: news.netvision.net.il 947320878 20104 62.0.172.81 (8 Jan 2000 08:41:18 GMT)
X-Complaints-To: abuse AT netvision DOT net DOT il
NNTP-Posting-Date: 8 Jan 2000 08:41:18 GMT
X-Mailer: Mozilla 4.7 [en] (Win98; I)
X-Accept-Language: en,ru,hebrew
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Jeff Williams wrote:
> 
> [1] It appears that INFOPATH must be a semicolon-separated directory
> list; a colon-delimited list does not work---even in bash, even with
> PATH_SEPARATOR=:

This is correct.  Since DOS/Windows use a colon as part of absolute
file names, it cannot be used for a separator in INFOPATH.  You must
use a semi-colon.  PATH_SEPARATOR=: only affects the handling of PATH,
and only Bash knows about PATH_SEPARATOR.

> Would/should/could I expect that a colon-delimited INFOPATH is
> somehow/someday possible?

What for?  All DJGPP ports (and native DOS/Windows programs) always
use a semi-colon in directory lists modeled after PATH.  DOS is not
Unix, no matter how well does DJGPP succeed to conceal that ;-).

> export INFOPATH='.;/gnuplot;/nasm/docs;'      does not work
> % info gnuplot
> info: dir: No such file or directory (ENOENT)

That's because DJGPP.ENV appends its own default value to what you put
into INFOPATH, so the doubled semi-colon ends up not being at the end
anymore, and instead passes to Info an invalid value of INFOPATH, one
with two semi-colons in a row.

Since DJGPP.ENV already appends the list of the default directories to
what you set INFOPATH to, I don't see any need to use this feature of
Info.  But if you can explain why do you need it, I could try to think
about possible work-arounds.