-
-
Notifications
You must be signed in to change notification settings - Fork 16.7k
installShellFiles: Allow installManPage to take a piped input #428382
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Though I think it would be good to leave open a bit before merging, in case someone else is strongly thinks the complexity of supporting pipes is not worth it
(I am curious what you want to use it for too)
I've come across some programs that output the manpages via stdin, so this is just a QOL thing, and brings it in line with the completion installer. Can see some with |
OK, yeah the grep convinces me. Also it "clicked" that since no one wants to write Troff, and there are lots of powerful in-code CLI frameworks these days, programs that programmatically generate their own man pages are becoming more common. |
Things done
--name
flag toinstallManPage
This change is backwards compatible because the script would fail if you provided a file named
--name
previously. It now doesn't fail if for some reason that is desired.--
argument to stop parsing flags afterpassthru.tests
.nixpkgs-review
on this PR. See nixpkgs-review usage../result/bin/
.Add a 👍 reaction to pull requests you find important.