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 request #13
Comments
Sorry you've had trouble with it! The good news is it's an easy fix. :) On this line, change Maybe cases like this should treat the |
Ahh. Thank you! If it is not really trivial to "treat the One problem that can occur, when trying to fix this, are name collisions. Example:
Especially in large usage messages, this can happen. Sure, the developer can avoid this, but then he really have to read the Docopt documentation! And priorization for this case is not really obvious to a new developer. An example how to use options with arguments in the README would be great and helpful. |
Well, I did, earlier today. :) Do you think that's enough, or that it should be more prominent? Or rather, do you think that that would've been enough to point you in the right direction if it had been in the README before? |
I commented on your commit. |
Thanks for that. I'll make those changes, and also update the haddock documentation to make note of this case. |
Take a look at 7283baa and see if that will work. I made the changes you suggested, and also added notes along side the haddock descriptions of the I'd like to eventually have everything that's currently in the README instead in a Let me know (open more issues) if anything else sticks out that could be made clearer! Otherwise, feel free to close this issue, and I'll upload the new docs to hackage. |
Thanks for your commitment :) And I added two comments on your commit. |
I try for days and don't get it work:
How to access an argument of an option (
... --out=file ...
)?I copied the first example from Hackage and added an argument to the option
--caps
. Then I added three lines at the bottom of themain
.I run the program and get an error:
Maybe it's a trivial error and anyone can help me?
The text was updated successfully, but these errors were encountered: