git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 3/3] parse-options: only insert newline in help text if needed

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 25, 2017, 05:53 UTC
Message-ID
<xmqqefqve33b.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<xmqqing7e3qs.fsf@gitster.mtv.corp.google.com>
Junio C Hamano <gitster@pobox.com> writes:
Show 17 quoted lines
> Brandon Casey <drafnel@gmail.com> writes:
>
>> Currently, when parse_options() produces a help message it always emits
>> a blank line after the usage text to separate it from the options text.
>> If the option spec does not define any switches, or only defines hidden
>> switches that will not be displayed, then the help text will end up with
>> two trailing blank lines instead of one.  Let's defer emitting the blank
>> line between the usage text and the options text until it is clear that
>> the options section will not be empty.
>
> This somehow looks familiar.  I think (together with the fix in 2/3)
> this makes it definitely better.  
>
> I also wonder if we want the final blank line, but that is sort-of a
> different issue.
>
> Thanks.

Oh, no wonder that this looked familiar. It solves the same issue as 48b8d3cf ("usage_with_options: omit double new line on empty option list", 2017-08-25) and of course it conflicts with it.

I find the solution presented with this patch is more direct and straightforward, leaving less chance to future breakage. Besides it comes with tests ;-), so perhaps I should drop the other one.

Previous: Junio C HamanoNext: Brandon Casey
Message 4 of 5 in “t0040,t1502: Demonstrate parse_options bugs”
  1. 1/3 t0040,t1502: Demonstrate parse_options bugsBrandon Casey, Sep 25, 2017
  2. 3/3 parse-options: only insert newline in help text if neededBrandon Casey, Sep 25, 2017
  3. Junio C HamanoSep 25, 2017
  4. Junio C HamanoSep 25, 2017
  5. 2/3 parse-options: write blank line to correct output streamBrandon Casey, Sep 25, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.