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

2014-03-21 Thread Junio C Hamano
Ilya Bobyr writes: >>> + ``, if specified, is used as a name of the argument in the >>> + help output, for options that take arguments. `` is >>> + terminated by the first whitespace. When output the name is shown in >>> + angle braces. Underscore symbols are replaced with spaces. >> The

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

2014-03-21 Thread Ilya Bobyr
On 3/20/2014 4:19 PM, Ilya Bobyr wrote: > On 3/20/2014 11:38 AM, Junio C Hamano wrote: >> Ilya Bobyr writes: >> >>> [...] >>> >>> -* SP+ help LF >>> +*? SP+ help LF >>> >>> ``:: >>> @@ -313,6 +313,12 @@ Each line of options has this format: >>> * Use `!`

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

2014-03-20 Thread Ilya Bobyr
On 3/20/2014 1:18 PM, Eric Sunshine wrote: On Thu, Mar 20, 2014 at 4:44 AM, Ilya Bobyr wrote: Built-in commands can specify names for option arguments when usage text is generated for a command. sh based commands should be able to do the same. Option argument name hint is any text that comes

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

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

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

2014-03-20 Thread Eric Sunshine
On Thu, Mar 20, 2014 at 4:44 AM, Ilya Bobyr wrote: > Built-in commands can specify names for option arguments when usage text > is generated for a command. sh based commands should be able to do the > same. > > Option argument name hint is any text that comes after [*=?!] after the > argument nam

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

2014-03-20 Thread Junio C Hamano
Ilya Bobyr writes: > Built-in commands can specify names for option arguments when usage text > is generated for a 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.

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

2014-03-20 Thread Ilya Bobyr
Built-in commands can specify names for option arguments when usage text is generated for a 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 are replaced with wh