git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Webb <chris@arachsys.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC 1/1] Add new indent-with-tab whitespace check
Date: Fri, 2 Apr 2010 11:55:04 +0100	[thread overview]
Message-ID: <20100402105504.GO19047@arachsys.com> (raw)
In-Reply-To: <7vsk7fovjx.fsf_-_@alter.siamese.dyndns.org> <7vwrwstq8r.fsf@alter.siamese.dyndns.org>

Hi. Thanks for the detailed feedback.

Junio C Hamano <gitster@pobox.com> writes:

> This sounds more like "tab-in-indent".  Naming the option that way would
> give it an added benefit of allowing it to be abbreviated to "tab" by the
> parser.

Yes that's nice: much harder to confuse with indent-with-non-tab that way.

> I think WS_TAB_IN_INDENT are incompatible with either WS_SPACE_BEFORE_TAB
> or WS_INDENT_WITH_TAB.  Don't we want to notice such a combination as an
> error?

Oh yes, that has to be the right behaviour for the finished feature here. (I
guess strictly they could coexist with the meaning 'no indented lines
allowed at all' but I don't think that's useful or sensible.)

> I'll queue this with s/indent-with-tab/tab-in-indent/ tweak to 'pu' but
> the topic would need:
> 
>  - detecting incompatible settings;
>  - tests;
>  - docs;
>  - matching change to apply --whitespace=fix;
> 
> before moving to 'next', I think.

Are you happy with my suggestion in [0/1] to replumb ws_fix_copy() to take a
strbuf as dst rather than a char *, to deal with the fact that whitespace
can grow with --whitespace=fix and WS_TAB_IN_INDENT?

If so, I'll polish up the existing patch as you suggest in your first three
points above, and then make this change to the way ws_fix_copy() works so I
can do the right thing in whitespace=fix.

> There is another issue with this change.  Because "whitespace" without any
> string in .gitattributes are defined to cause all the whitespace breakages
> known to git to be caught, and tab-in-indent is inherently incompatible
> with indent-with-non-tab, this cannot be supported without changing the
> definition of "default set of whitespace breakage classes".

Ah, this was a behaviour I didn't know about. I should probably put your
patch (without the WS_TAB_IN_INDENT line) as the first one in the series,
before I introduce WS_TAB_IN_INDENT, so we don't break this wildcard
whitespace behaviour at any point in the series.

Cheers,

Chris.

      parent reply	other threads:[~2010-04-02 10:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-27 14:08 [RFC 0/1] diff --check for indent-with-spaces style Chris Webb
2010-03-27 14:08 ` [RFC 1/1] Add new indent-with-tab whitespace check Chris Webb
2010-03-31 16:23   ` Junio C Hamano
2010-04-01 18:51     ` Re* " Junio C Hamano
2010-04-01 19:02       ` Junio C Hamano
2010-04-02 10:55     ` Chris Webb [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=20100402105504.GO19047@arachsys.com \
    --to=chris@arachsys.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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).