[pull] master from clap-rs:master #22
Open
+100,683
−33,636
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
![pull[bot]](https://avatars.githubusercontent.com/in/12910?s=60&v=4){kind=small}
fix(help): Style arg groups
fix(complete): Put clap in chage of Fish ordering
Support `allow_hyphen_values` in native completions
No idea why using passing along `IFS` isn't workong on my machine (but is for tests). Fixes #5730
fix(complete): Adjust how IFS is passed to clap
docs(complete): Clarify CompleteEnv's Shell trait
fix(complete): Strip wrappers for running completer
Turns out to be another win in case the suggestions feature is enabled Signed-off-by: Daniel Egger <[email protected]>
…sertion-sort Replace another sort_by call by a manual insertion with a binary_search
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
feat(mangen): Separate options based on `help_heading`
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Inspired by https://www.reddit.com/r/rust/comments/1i5np88/clap_documentation_is_too_confusing_for_me/m87mutm/ > > I always use derive, and I mostly use the reference. From manual > experimentation I’ve had to develop the mental model that short > implicitly is what makes an argument non-positional, and if I want an > argument to be positional then it will be by default unless I specify > short. When I search for the word “positional” in the reference, there > are no results. When I search for it in the tutorial, there is one > result that says something I can do with an argument that i’ve made > positional, but there’s no indication for how to make the argument > positional in the first place. The reference documentation on short > doesn’t mention anything about the fact that that’s what determines > whether an argument is positional, even when I click through to the > builder documentation on Arg::short.
docs: Clarify the default state of an Arg/field
With the new-ish rustdoc header sidebar, hopefully this will make this layout easiest to deal with. By having everything on one page, people are less likely to miss something, especially if they use their browsers search.
docs(tutorial): Experiment with a flat layout
fix formatting
fix(complete): Fix single quote escaping in PowerShell
fix(complete): Check if help string is empty
You can remove the env variable but sometimes you want to override it.
feat(complete): Provide a way to disable env completions
chore(deps): Update Rust crate clap-cargo to 0.15.0
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.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.1)
Can you help keep this open source service alive? 💖 Please sponsor : )