On Wed, Dec 05, 2007 at 01:49:30PM -0500, Clint Adams wrote:
> On Wed, Dec 05, 2007 at 05:45:46PM +0000, Colin Watson wrote:
> > Adam Katz wrote:
> > > In the event there IS an empty string in handed to the loop on line 46,
> > > nothing will happen unless the argument ("$PROGRAM") happens to exist as
> > > a file in / with executable permissions (assuming you remove lines
> > > 47-49, otherwise it searches the current directory).
> >
> > I believe that Clint is incorrect that this was the intent; it certainly
> > wasn't my intent, as that does not correspond to the shell's command
> > search semantics. It's just an unremarkable accident of the obvious
> > implementation. ELEMENT is not supposed to be empty in that case branch.
>
> I'm afraid I'm either misunderstanding the original message or Colin's
> reply, though I'm not sure it matters for practical disposition of this
> bug.
My point was that it is not intended that 'which' should look for an
executable file in / if it somehow ends up with an empty PATH element at
that point; it should only look for an executable file in / if / is
explicitly in PATH. I may have misunderstood exactly what you were
replying to when you said "I believe this is the intent", though.
I agree it doesn't matter for the purposes of disposing of this bug.
Thanks,
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
