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

Re: Whitespace options

From
Miles Bader <miles@gnu.org>
Date
Apr 3, 2009, 02:39 UTC
Message-ID
<buoab6yjw9m.fsf@dhlpc061.dev.necel.com>
In-Reply-To
<3C72F4A7-9B7A-44D0-B13D-FD534EB02C27@bitart.com>
Gerd Knops <gerti-git@bitart.com> writes:
> The reason is that many editors (especially those supporting indent-
> based code folding) keep 'empty' lines at the current indentation
> level. git (with default settings) flags all those lines.

That sounds like very fragile behavior on the part of the editor -- it sounds like they assume that all source code was created by their editor, and will never be touched by any other tool...

-Miles
-- 
Suburbia: where they tear out the trees and then name streets after them.
Previous: Joshua Juran
Message 3 of 3 in “Whitespace options”
  1. Gerd KnopsApr 2, 2009
  2. Joshua JuranApr 3, 2009
  3. Miles BaderApr 3, 2009

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.