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

Re: [PATCH] pretty-formats.txt: fix whitespace

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 26, 2023, 16:42 UTC
Message-ID
<xmqqo7hoophh.fsf@gitster.g>
In-Reply-To
<CACZqfqCfvWASMPMxRpRuAUQPcprcB4RHxxke_qTZ3bFGLf3T8Q@mail.gmail.com>
Josh Soref <jsoref@gmail.com> writes:
> As it (IMO) takes effort (admittedly trivial, and quite likely
> habitual) to insert a second space, I assume that this was a desired
> thing and the one space was the aberration, hence the patch went in
> favor of two spaces.

Back in typewriter days, people were taught to leave two spaces after a full stop, because on monospace output it was easier to read that way. Then the desktop publishing software came and people were encouraged to leave the appearance up to the software.

So to old timers who have already been trained to type two spaces after a sentence, it takes more effort not to type the space bar twice.

But as I said already, I personally feel that the consistency guidelines around this area should be:

 (1) it would be nice if a new document does not use mixed style, but
 (2) it is not worth the patch noise only to "fix" them one way or
     the other.

Here "patch noise" does not primarily mean the effort a producer of such a patch spends making sure what they did is correct. The cost of making sure unrelated mistakes do not slip into the codebase and documentation without being noticed is much higher for such a patch that ought to be a mechanical conversion.

Thanks.
Previous: Josh Soref
Message 10 of 10 in “pretty-formats.txt: fix whitespace”
  1. pretty-formats.txt: fix whitespaceJosh Soref via GitGitGadget, Sep 22, 2023
  2. Junio C HamanoSep 22, 2023
  3. Josh SorefSep 24, 2023
  4. Junio C HamanoSep 25, 2023
  5. Linus ArverSep 26, 2023
  6. Josh SorefSep 26, 2023
  7. Linus ArverSep 26, 2023
  8. Kristoffer HaugsbakkSep 25, 2023
  9. Josh SorefSep 26, 2023
  10. Junio C HamanoSep 26, 2023

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.