Handling manpages
See original GitHub issueHow would this feature be useful?
Some packages, like ipython
and ranger-fm
come with man pages. It would be nice to provide these, such that man ipython
will work.
Describe the solution you’d like
Much like we ask users to ensure ~/.local/bin is on their PATH and we manage symlinks there. We could manage symlinks to man pages in a location and ask them to add a MANDATORY_MANPATH or MANPATH_MAP line to their .manpath file.
Describe alternatives you’ve considered
I tried globbing ~/.local/pipx/venvs/*/share/man in my man config. But didn’t succeed. Adding a line for each installed package does work as expected, so that’s why I think automating the process would be ideal.
I’m willing and able to implement this. I just wanted to open discussion first instead of immediately coming with an elaborate PR.
Issue Analytics
- State:
- Created a year ago
- Reactions:5
- Comments:6 (2 by maintainers)
Top GitHub Comments
Option 1 is probably the easiest path for now since there’s no suitable metadata for specifying file location now (entry point is close but it’s designed for Python files and I’m not sure if people would think it’s a good idea for us to use it like this). If enough projects catch on, we’d have more ground to push for a metadata standard.
So the next steps for anyone interested in implementing this would be:
${DATA_DIRECTORY}/data/share/man/
.${PIPX_HOME}/share/man
, like we do for entry points (inside${PIPX_HOME}/bin
).The following script seems to work for me. I called it
pipx-manpage-install
.You need to have
stow
installed. Forman
to find the manpages,~/.local/share/man
needs to be in the output of themanpath
command. It is there on my debian system by default, though I’m not sure how it got there.The --ignore pattern comes from https://unix.stackexchange.com/a/293676/261949.