git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miles Bader <miles@gnu.org>
To: Gerd Knops <gerti-git@bitart.com>
Cc: git@vger.kernel.org
Subject: Re: Whitespace options
Date: Fri, 03 Apr 2009 11:39:33 +0900	[thread overview]
Message-ID: <buoab6yjw9m.fsf@dhlpc061.dev.necel.com> (raw)
In-Reply-To: <3C72F4A7-9B7A-44D0-B13D-FD534EB02C27@bitart.com> (Gerd Knops's message of "Thu, 2 Apr 2009 14:18:19 -0500")

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.

      parent reply	other threads:[~2009-04-03  2:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-02 19:18 Whitespace options Gerd Knops
2009-04-03  2:15 ` Joshua Juran
2009-04-03  2:39 ` Miles Bader [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=buoab6yjw9m.fsf@dhlpc061.dev.necel.com \
    --to=miles@gnu.org \
    --cc=gerti-git@bitart.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).