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
brew docs
as an alias for open https://docs.brew.sh
#13834
Comments
I'm open to a |
I love, admire and agree with the honest admission of laziness here. Given how little code would be required to implement this: would definitely review a PR. |
These may well not be blocking comments regarding an initial implementation, as these could also be potential future extensions to an initial minimum viable product, but I have a few additional thoughts on some things to keep in mind for this kind of functionality:
|
Thanks for the feedback. I also wondered, since I have never used linuxbrew, whether Linux, which uses a different command, should be supported as well? Meaning whether it should be the Ruby equivalent of
Reference: https://linux.die.net/man/1/xdg-open |
|
As the maintainers would mention/point out, Linuxbrew got merged into Homebrew proper a while back (see Linuxbrew/brew#612, #7028, and the v1.9.0 and v3.3.0 release blog posts for some of the historical details.) |
Additional thoughts for add-ons:
|
Provide a detailed description of the proposed feature
brew docs
as a shortcut foropen https://docs.brew.sh
Also udpate brew help
What is the motivation for the feature?
Laziness is one of the three great virtues of the programmer, as defined by Larry Wall.
Laziness is the quality that makes you go to great effort to reduce overall energy expenditure. It makes you write labor-saving programs that other people will find useful and document what you wrote so you don't have to answer so many questions about it.
How will the feature be relevant to at least 90% of Homebrew users?
Benefits for users
It makes it marginally easier to 90% of Homebrew users to access the docs at https://docs.brew.sh
And maybe find the information they need, which is nice.
Benefits for maintainers
It is marginally nicer for Homebrew maintainers that Homebrew users are empowered to find the documentation they need. They would have to repeat themselves marginally less.
Of course, many users still won't read the docs, but now maintainers can reply
This kind of reply makes it marginally more likely that users read the docs next time.
Yes it's just a RTFM, but I think/hope it's an empowering "Read the Friendly Manual" RTFM, not the "Read the Fucking Manual" RTFM.
Benefits for documentation writers
As someone who writes technical documentation myself, I know this is hard work and I know that I like it when more users actually use and benefit from the documentation.
What alternatives to the feature have been considered?
Bookmarking https://docs.brew.sh
But I'm too lazy to bookmark things and use browser bookmarks correctly.
The text was updated successfully, but these errors were encountered: