-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OS X: read /etc/manpaths and /etc/manpaths.d #1092
Comments
Sounds reasonable |
OS X uses a tool To that end, if we do adopt this same behavior (and we don't decide to do it by invoking |
@kballard I wrote this blog article about why MANPATH doesn't work on OS X less than six months ago. I admit I did not expend much effort in figuring out why it didn't work. But I eventually gave up and added the following comment to my environ.fish file (and before that the equivalent zsh file) which is sourced from my ~/.config/fish/config.fish file:
I would not be offended to learn that despite using OS X for over a decade I misunderstood this aspect of its behavior. |
@krader1961 That blog post is rather perplexing, because I just tried and it worked just fine.
If I run a Bash login shell with that |
I've so far never had any issues with OS X ignoring or not respecting |
…1092. * Only append paths if `MANPATH` is already set, to match behavior of macOS `path_helper` utility. * Use the same technique as is used above to set PATH from /etc/paths and /etc/paths.d/*.
This has been resolved but wasn't automatically closed because the commit did not include the magic line "Fixes #1092". |
Similar to
/etc/paths
and/etc/paths.d
OS X has/etc/manpaths
and/etc/manpaths.d
which should be used to populate the$MANPATH
environment variable.The text was updated successfully, but these errors were encountered: