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

core.whitespace blank-at-eof on by default?

From
DSDan Savilonis <djs@n-cube.org>
Date
Apr 23, 2010, 14:58 UTC
Message-ID
<u2k325c62f61004230758xc5dbd87dza2515fac8e2e505b@mail.gmail.com>

I noticed the blank-at-eof whitespace error is on by default after 77b15bb. As a result, correcting a C file with no blank line at EOF is marked as a whitespace error, even though the C standard requires this.

What is the intent of this rule? To prevent extra blank lines at EOF, or any at all? Would it make more sense to only warn only one the addition of 2+ blank lines or when a blank line is already present at EOF?

Dan
Message 1 of 1 in “core.whitespace blank-at-eof on by default?”
  1. Dan SavilonisApr 23, 2010

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.