doc: Added information on --indent to --help

[EvanCarroll]

Simple doc patch when I noticed functionality I already need was there just undocumented.

[pkoppstein]

Since --indent requires an argument, an argument should be mentioned in usage(). Following the manual, --indent n would be appropriate.

The larger point here is that documenting all the options in usage() in this manner would increase the size of the executable quite a lot, and goes against the idea of keeping the executable small by providing details online.

I would propose that usage() simply provide a synopsis of all the options (in the usual man page style), leaving the descriptive details of the options to the online documentation.

[EvanCarroll]

@pkoppstein the patch was already amended 12 hours before your comment to include n. And you're talking about a couple of bytes of text. Hardly something that will "increase the size of the executable quite a lot."

[pkoppstein]

@EvanCarroll - You apparently overlooked the phrase “ … documenting all the options in usage() …”.

(The screen I was looking at only showed the line without the “n”.)

[wader]

I would not worry about binary size either, possibly that the text is getting long, but maybe then we should cut down on some other usage text instead? maybe the stuff about IEEE754 numbers etc

[itchyny]

I'm not worried about the executable size due to this help, we should list all the option #2284 (we should rather consider replace the builtins by C-coded internals). The only concern about this PR is about the newline in the description; can Bash's _parse_help parse this form?

[itchyny]

Looks OK.

 $ _parse_help jq -h | xargs
-c -n -e -s -r -R -C -M -S --tab --arg --argjson --slurpfile --rawfile --args --jsonargs --
 $ _parse_help ./jq -h | xargs
-c -n -e -s -r -R -C -M -S --tab --indent --arg --argjson --slurpfile --rawfile --args --jsonargs --

[itchyny]

Oops, -1 is not 4 spaces, but the tab character.