From:	"David" <nobody AT bogus DOT org>
Newsgroups:	comp.os.msdos.djgpp
References:	<44An5.13355$Gs DOT 66133 AT news4 DOT atl> <7QWn5.142399$Fw6 DOT 3484407 AT afrodite DOT telenet-ops DOT be> <jz7o5.1187$Mw DOT 11451 AT news2 DOT atl> <5567-Mon21Aug2000143151+0300-eliz AT is DOT elta DOT co DOT il>
Subject:	Re: DJGPP port of WHICH
Lines:	34
X-Newsreader:	Microsoft Outlook Express 4.72.3110.5
X-MimeOLE:	Produced By Microsoft MimeOLE V4.72.3110.3
Message-ID:	<Y13p5.7909$Ez6.48830@news3.atl>
Date:	Thu, 24 Aug 2000 02:13:00 -0400
NNTP-Posting-Host:	209.214.202.15
X-Trace:	news3.atl 967097592 209.214.202.15 (Thu, 24 Aug 2000 02:13:12 EDT)
NNTP-Posting-Date:	Thu, 24 Aug 2000 02:13:12 EDT
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

I played around with the __dosexec_find_on_path function, but it
would require major changes to the original "which.c" source code
to support the "-a" switch.  The "-a" switch is the reason I
wanted to use "which" to begin with, as I have 3 different
versions of grep on my system, and I like to be able to check
which one I will be calling.

Questions:
1. Is there enough of a demand for a DJGPP version of which for it
to be worthwhile to change the "which.c" to use the
__dosexec_find_on_path and still support the "-a" switch?
2. Would anyone be interested in a version of "which" that allows
the user to specify extra search extensions in an environment
variable?  This would be useful for finding Perl scripts, Windows
NT ".cmd" files, and other interesting executables.

Eli Zaretskii wrote in message
<5567-Mon21Aug2000143151+0300-eliz AT is DOT elta DOT co DOT il>...
>> From: "David" <nobody AT bogus DOT org>
>> Newsgroups: comp.os.msdos.djgpp
>> Date: Mon, 21 Aug 2000 06:28:18 -0400
>>
>> What is the "bash exec-finding code"?  I added this little hack
to
>> search a list of extensions:


...deleted hack

>There is a library function which will do all this: it's called
>__dosexec_find_on_path.

- Raw text -