Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Find path to an executable

+5
−0

How to find the exact path to an executable file present in your PATH. I.e. commands you can call by just their names.

E.g. what executable gets called when I type find and hit enter?

$ hypothetical-find-path find
/path/to/find
History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

0 comment threads

3 answers

You are accessing this answer with a direct link, so it's being shown above all other answers regardless of its score. You can return to the normal view.

+1
−0

If you need this in a portable POSIX-compliant script, you should not use which but this instead:

command -v find
History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

0 comment threads

+7
−0

which only tells you about a path that would be found in PATH. Often, people who think they have this question have a more general question - i.e., what will be used when the named command is requested. In particular, aside from being executables on PATH, commands can also refer to shell builtins.

The type command gives this information. With the -a flag, it can also disclose multiple implementations of a command, in preference order. For example, on my system:

$ type -a echo
echo is a shell builtin
echo is /usr/bin/echo
echo is /bin/echo

The echo executable on my system is hard-linked in those locations, but neither would ordinarily be used (as the shell builtin would be preferred).

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

2 comment threads

Details I just found on Stack Exchange (1 comment)
which can also give more information (1 comment)
+4
−0

GNU which does the trick:

$ which find
/usr/bin/find

It's very likely already installed.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

0 comment threads

Sign up to answer this question »