Neither 'command -v scan' nor 'which scan' works for me. I want to name the
script, from which I want to know where nmh's scan is located. "scan". I want
to know its location so I can invoke it. Of course, I know its location today,
/usr/local/nmh/bin/scan. But I would prefer something more robust. Again, I
could search, $PATH for a component containing "/nmh.", but how do I know that
in the future there won't be more than one such component, or that in the
future there will be any such component? All that depends on how I will
configure nmh in the future.
Ralph Corderoy <ralph(_at_)inputplus(_dot_)co(_dot_)uk> writes:
Hi Norm,
How, from a script, can I get the location of the nmh executables.
Depends on the shell. Try
$ command -v inc
/usr/bin/mh/inc
$
If there's a shell function called `inc' though then it may describe
that.
the location of the "user" executables, like scan.
Why do you need to know?
Cheers, Ralph.
_______________________________________________
Nmh-workers mailing list
Nmh-workers(_at_)nongnu(_dot_)org
https://lists.nongnu.org/mailman/listinfo/nmh-workers
Norman Shapiro
_______________________________________________
Nmh-workers mailing list
Nmh-workers(_at_)nongnu(_dot_)org
https://lists.nongnu.org/mailman/listinfo/nmh-workers