Massage --help text to use max 72 characters width

[wader]

No description provided.

[emanuele6]

Can you limit it to 72 characters instead? That is my personal preference for line character limit; and that is the character limit the top part of the output of jq --help is using.

[wader]

@emanuele6 adjusted to 72, looks like this now:

Command options:
  -n, --null-input          use `null` as the single input value;
  -R, --raw-input           read each line as string instead of JSON;
  -s, --slurp               read all inputs into an array and use it as
                            the single input value;
  -c, --compact-output      compact instead of pretty-printed output;
  -r, --raw-output          output strings without escapes and quotes;
      --raw-output0         implies -r and output NUL after each output;
  -j, --join-output         implies -r and output without newline after
                            each output;
  -a, --ascii-output        output strings by only ASCII characters
                            using escape sequences;
  -S, --sort-keys           sort keys of each object on output;
  -C, --color-output        colorize JSON output;
  -M, --monochrome-output   disable colored output;
      --tab                 use tabs for indentation;
      --indent n            use n spaces for indentation (max 7 spaces);
      --unbuffered          flush output stream after each output;
      --stream              parse the input value in streaming fashion;
      --stream-errors       implies --stream and report parse error as
                            an array;
      --seq                 parse input/output as application/json-seq;
  -f, --from-file file      load filter from the file;
  -L directory              search modules from the directory;
      --arg name value      set $name to the string value;
      --argjson name value  set $name to the JSON value;
      --slurpfile name file set $name to an array of JSON values read
                            from the file;
      --rawfile name file   set $name to string contents of file;
      --args                consume remaining arguments as positional
                            string values;
      --jsonargs            consume remaining arguments as positional
                            JSON values;
  -e, --exit-status         set exit status code based on the output;
  -V, --version             show the version;
  -h, --help                show the help;
  --                        terminates argument processing;

[wader]

I guess we can remove "on Windows" if we do it conditionally?

[emanuele6]

$ ./jq --help >/dev/null 2>&1 | jq -nR 'all(inputs; . <= 72)'
true

[emanuele6]

The commit message still says 80 instead of 72, but that can be fixed on GitHub selecting the `Squash and merge" merge option, so if you don't need to change the code further, just leave it as is so the CI doesn't need to re-run.

[wader]

The commit message still says 80 instead of 72, but that can be fixed on GitHub selecting the `Squash and merge" merge option, so if you don't need to change the code further, just leave it as is so the CI doesn't need to re-run.

Updated the commit message and github issue title, but the branch name will say 80

[emanuele6]

The name of the branch doesn't matter ^^
But GitHub gives you the opportunity to fix typos in commit messages before merging/rebasing selecting the "Squash and merge" option, I could have used that before merging to change 80 to 72; now that you have re-committed the CI needs to re-run, but no big deal. =)

[wader]

The name of the branch doesn't matter ^^ But GitHub gives you the opportunity to fix typos in commit messages before merging/rebasing selecting the "Squash and merge" option, I could have used that before merging to change 80 to 72; now that you have re-committed the CI needs to re-run, but no big deal. =)

Ah yes we don't use merge commits so branch name will not appear. Sorry for retrigger.

[nicowilliams]

Thanks!