-
Notifications
You must be signed in to change notification settings - Fork 266
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
getting_started - custom location - wrong MANPATH #493
Comments
I suspect that the correct answer to this may depend on what linux system and/or configuration and/or clj install process is in play. I really want to avoid turning this page into a treatise on linux man page configuration so maybe it would be better to not doc the precise mechanism here at all and just suggest possible changing one ofman_dev.conf, MANPATH etc. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The getting_started page's Custom Location section gives the following example:
Allowing for a different prefix that I gave the installer, the second location does not exist. I think the second location's "/man" should be "/share/man".
The long story is that, to avoid sudo, I could not follow the instructions precisely. Here's what I did to run into the problem and how I resolved it. I suppose that the resolution also applies to the sudo-related case illustrated on getting_started.
Instead of changing a man-related configuration in
/etc
, I added the following line to.bash_profile
:(Initial colon important to indicate that this is an addendum to system locations.) I activated the new MANPATH with
source .bash_profile
. Butman -u clj
did not yield any results.After changing to
the
man -u clj
command worked.The text was updated successfully, but these errors were encountered: