On 3/20/2014 4:19 PM, Ilya Bobyr wrote:
On 3/20/2014 11:38 AM, Junio C Hamano wrote:
Ilya Bobyr ilya.bo...@gmail.com writes:
[...]
-opt_specflags* SP+ help LF
+opt_specflags*arg_hint? SP+ help LF
`opt_spec`::
@@ -313,6 +313,12 @@ Each line of options
Ilya Bobyr ilya.bo...@gmail.com writes:
+ `arg_hing`, if specified, is used as a name of the argument in the
+ help output, for options that take arguments. `arg_hint` is
+ terminated by the first whitespace. When output the name is shown in
+ angle braces. Underscore symbols are
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
Ilya Bobyr ilya.bo...@gmail.com 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
On Thu, Mar 20, 2014 at 4:44 AM, Ilya Bobyr ilya.bo...@gmail.com 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
On 3/20/2014 11:38 AM, Junio C Hamano wrote:
Ilya Bobyr ilya.bo...@gmail.com 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
On 3/20/2014 1:18 PM, Eric Sunshine wrote:
On Thu, Mar 20, 2014 at 4:44 AM, Ilya Bobyr ilya.bo...@gmail.com 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
7 matches
Mail list logo