Closed marcransome closed 3 years ago
I'm cautious of introducing Fisher-only features. My intention is not really to extend out-of-the-box Fish, but to make it easier to install, update, and remove "plugins", which essentially inherit their look and feel from ~/.config/fish
.
For some history, we used to have man
page support in 1.x~2.x, but I ended up removing it. AFAIK ~/.config/fish/manpages
is not a special place for users to deposit general-purpose man pages that Fish knows about.
I'd like to hear what you think. Maybe we can agree to support this in a different form, perhaps even through a third-party plugin.
I'm still interested in having that discussion, but I haven't received a reply in a while, so I'm just going to close for now.
@jorgebucaran I've been toying with the ability to install man pages with
fisher
plugins and would like your input if possible. The changes I've proposed here add basic functionality for man pages, and can be seen to work when using the pond plugin:The man page should be available as expected:
Files matching the pattern
manpages/<name>.<section-number>
are installed to$fisher_path/manpages
and symbolic links are created at/usr/share/man/man<section-number>/<name>.<section-number>
. Manual files and symbolic links are removed when a plugin is uninstalled.I'd like to get some feedback regarding the changes, as well as any thoughts you might have on how to handle different locales (e.g.
<my-project>/manpages/<locale>/<name>.<section-number>
. 🤔