Re: [PATCH] rev-parse --parseopt: option argument name hints

On 3/19/2014 11:46 AM, Junio C Hamano wrote: Ilya Bobyr writes: I can not find this particular patch in the latest "What's cooking" email. Is there something I can do? IIRC, I think I was waiting for the version with a new "Usage text" section to the documentation you alluded to in this excha

Re: [PATCH] rev-parse --parseopt: option argument name hints

Ilya Bobyr writes: > I can not find this particular patch in the latest "What's cooking" email. > Is there something I can do? IIRC, I think I was waiting for the version with a new "Usage text" section to the documentation you alluded to in this exchange ($gmane/243924): Ilya Bobyr writes

Re: [PATCH] rev-parse --parseopt: option argument name hints

On 3/12/2014 9:59 AM, Junio C Hamano wrote: Ilya Bobyr writes: I though that an example just to describe `argh' while useful would look a bit disproportional, compared to the amount of text on --parseopt. But now that I've added a "Usage text" section to looks quite in place. Good thinking.

Re: [PATCH] rev-parse --parseopt: option argument name hints

Ilya Bobyr writes: > I though that an example just to describe `argh' while useful would > look a bit disproportional, compared to the amount of text on > --parseopt. > > But now that I've added a "Usage text" section to looks quite in place. Good thinking. > I was also wondering about the poss

Re: [PATCH] rev-parse --parseopt: option argument name hints

On 3/11/2014 12:10 PM, Junio C Hamano wrote: Junio C Hamano writes: Documentation on the whole argument parsing is quite short, so, I though, adding an example just to show how usage is generated would look like I am trying to make this feature look important than it is :) You already are by

Re: [PATCH] rev-parse --parseopt: option argument name hints

Junio C Hamano writes: >> Documentation on the whole argument parsing is quite short, so, I >> though, adding an example just to show how usage is generated would >> look like I am trying to make this feature look important than it is >> :) > > You already are by saying the "Angle brackets are au

Re: [PATCH] rev-parse --parseopt: option argument name hints

Ilya Bobyr writes: > On 3/4/2014 11:22 AM, Junio C Hamano wrote: >> Ilya Bobyr writes: >>> @@ -333,6 +339,7 @@ h,helpshow the help >>> foo some nifty option --foo >>> bar= some cool option --bar with an argument >>> +baz=arg another cool option --baz with an argument named

Re: [PATCH] rev-parse --parseopt: option argument name hints

On 3/4/2014 11:22 AM, Junio C Hamano wrote: Ilya Bobyr writes: Built-in commands can specify names for option arguments, that are shown when usage text is generated for the command. sh based commands should be able to do the same. Option argument name hint is any text that comes after [*=?!]

Re: [PATCH] rev-parse --parseopt: option argument name hints

Ilya Bobyr writes: > Built-in commands can specify names for option arguments, that are shown > when usage text is generated for the command. sh based commands should > be able to do the same. > > Option argument name hint is any text that comes after [*=?!] after the > argument name up to the f

[PATCH] rev-parse --parseopt: option argument name hints

Built-in commands can specify names for option arguments, that are shown when usage text is generated for the command. sh based commands should be able to do the same. Option argument name hint is any text that comes after [*=?!] after the argument name up to the first whitespace. Underscores ar