On 11/23/24 17:23, Simon Tatham wrote:
Pádraig Brady wrote:
All these boil down to you want to pass the actual path
rather than lookup a name in $PATH.
This can be achieved simply with: env $(realpath -ms "$path")
True – and that's what build systems wrapping 'make' often do (perhaps
in-proce
Pádraig Brady wrote:
> All these boil down to you want to pass the actual path
> rather than lookup a name in $PATH.
> This can be achieved simply with: env $(realpath -ms "$path")
True – and that's what build systems wrapping 'make' often do (perhaps
in-process or at makefile-construction time),
On 23/11/2024 09:14, Simon Tatham wrote:
Simon Tatham wrote:
I think it would be useful if 'env' had an option which would cause it
to treat its COMMAND argument as _necessarily_ a pathname to an
executable file, rather than the usual semantics of considering it to be
either that or a command t
Simon Tatham wrote:
> I think it would be useful if 'env' had an option which would cause it
> to treat its COMMAND argument as _necessarily_ a pathname to an
> executable file, rather than the usual semantics of considering it to be
> either that or a command to search for on PATH.
Rob Landley w
On 11/22/24 08:15, Simon Tatham wrote:
I think it would be useful if 'env' had an option which would cause it
to treat its COMMAND argument as _necessarily_ a pathname to an
executable file, rather than the usual semantics of considering it to be
either that or a command to search for on PATH.
