clarify radius flag #49
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Airblader
approved these changes
Jul 7, 2019
|
Hey, thanks for the PR. You're absolutely right that this should be more clear. Much appreciated! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reading the man page, I was briefly confused about how
--jitterwas supposed to work. I thought it should be clarified.I thought of adding an issue: "Please clarify this flag", but, although I'm not 100% sure this is how it works (I read a bit of the source & some Xlib man pages, but I could still be wrong), I imagine the maintainer knows immediately whether or not it's correct. If it is, merging this is easier than responding to an issue.