better display of optional arguments in bzr help
Bug #62250 reported by
Martin Pool
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Confirmed
|
Wishlist
|
Unassigned | ||
| Breezy |
Triaged
|
Wishlist
|
Unassigned | ||
Bug Description
Jari Aalto suggests
https:/
the help message should actually display
bzr checkout [BRANCH [TO_LOCATION]]
since if only one argument is given it's the first.
Revision history for this message
| John A Meinel (jameinel) wrote | #1 |
| Changed in bzr: | |
| importance: | Untriaged → Wishlist |
| status: | Unconfirmed → Confirmed |
| tags: | added: check-for-breezy |
| tags: | removed: check-for-breezy |
| Changed in brz: | |
| status: | New → Triaged |
| importance: | Undecided → Wishlist |
| tags: | added: bitesized help |
To post a comment you must log in.
Our optional arguments are always required in order. It is probably standard practice to nest as mentioned. I'm concerned about entries which take lots of optional arguments, as it starts to get unclear at about 3:
bzr foo [ONE [TWO [THREE]]]
versus
bzr foo [ONE] [TWO] [THREE]
*however*, core probably doesn't have any commands that take more than 2 optional positional arguments, so we should be able to use standard notation.