-
Notifications
You must be signed in to change notification settings - Fork 18
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
help target #13
Comments
I agree with 1, but I disagree with 2. The reason to write a canned recipe for the help text is readibility (and extensibility). The heredoc and In detail:
|
I tend to generate the help file by parsing target and variable declarations with their comments and then outputting help:
echo "Targets"
echo ""
echo " some-target Comment describing some-target. etc. Not important enough to argue about. |
i know. I do it like that myself. For short texts. But as I said: readability and extensibility. You forgot a closing quote BTW ;-) |
Classic... |
Two proposals:
help
the default targetis a convention I really like because when it is not completely obvious what the default should be (and I argue it is not for this repo) then it's better not to do anything for the default and just print usage info.
Evaluating a variable that cats a heredoc string seems convoluted. Also why export
HELP
?The text was updated successfully, but these errors were encountered: