19.7 C
New York
Wednesday, June 18, 2025

terminal – MANPATH, ‘whereis’ and the way manuals are positioned?


I exploit a 2023 M2 MBP working Ventura 13.7.2. To reinforce Apple’s relatively paltry choices of CL utilities, I rely on MacPorts. Sadly, MacPorts doesn’t have a substitute/different for whereis.

In case you’ve ever used Apple’s native whereis you might have seen that it has some shortcomings; e.g.:

/usr/bin/whereis discover
discover: /usr/bin/discover /decide/native/libexec/gnubin/man/man1/discover.1.gz

First – it solely studies on native apps. Its app searches are restricted by Apple, and apparently this can’t be over-ridden by any consumer.

Second – as you may see above, it has no such restrictions on trying to find manuals. On this case, it studies on the guide location for the discover instrument which was put in from MacPorts.

Third – the native whereis discovered the manpage for discover with out advantage of the MANPATH atmosphere variable – it’s not set on my system.

Fourth – AFAIK, that leaves solely manpath (one other Apple-sourced CL utility) as a useful resource for locating the situation of manuals. Nevertheless, as I learn man manpath – it isn’t getting it from there both!

In order that’s my query: How does Apple’s whereis command discover the situation of system manuals? Have I mis-read man manpath? Can somebody clarify the method?

Additionally, I would have an interest to know if Apple publishes the supply recordsdata for manpath and whereis, and if that’s the case – the place can I discover them?

Related Articles

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Latest Articles