Re: command -v ../foo when ../foo is a directory

[Simon Josefsson <simon@josefsson.org>]

[-- Attachment #1: Type: text/plain, Size: 807 bytes --]

Harald van Dijk <harald@gigawatt.nl> writes:

> POSIX says for command -v:
>
>> Utilities, regular built-in utilities, command_names including a
>   <slash> character, and any implementation-defined functions that are 
> found using the PATH variable (as described in Command Search and
> Execution), shall be written as absolute pathnames.
>
> ../bar is a command_name including a <slash> character. There is
> nothing in here that says to check whether it is executable, POSIX
> just says to write it as an absolute pathname, and that is what dash
> does.

Interesting, thank you!  It looks like a bug in the POSIX specs, perhaps
we can get it clarified?  Either by mandating a particular behaviour
going forward, or at least acknowledge the different interpretations
somehow.

/Simon

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 255 bytes --]