unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Daniel Hackney <dan@haxney.org>
Cc: emacs-devel@gnu.org, Miles Bader <miles@gnu.org>
Subject: Re: The grand indentation unification project
Date: Mon, 28 May 2012 01:12:03 -0400	[thread overview]
Message-ID: <jwvzk8sucaf.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CAMqXDZti6sMmYbQ6f-imrH3RG1=+tK3yPMB_f1-qCG_n9G6bYA@mail.gmail.com> (Daniel Hackney's message of "Sun, 27 May 2012 13:32:13 -0400")

> Yes, it would, but the idea would be to set `indent-tabs-mode' to t, add
> `whitespace-cleanup to `before-save-hook', and have a single massive,
> horrible, ugly "whitespace unification" commit, and then everything after
> that follows the tab indent and whitespace styles. That way, you'd have one
> big patch with all the whitespace changes, but future patches wouldn't have
> any whitespace-only diffs.

Still sucks for everyone who's got a branch to keep in sync.

The problems you complain about (conflicts due to whitespace changes)
pretty much only show up because of such "helpful" commits.

So, no, we don't want any of that.  OTOH we would accept changes which
will enforce such "canonical spacing" in future commits (i.e. enforce
this canonicity but only on lines which are already changed for other
reasons anyway, thus not introducing new gratuitous conflicts).


        Stefan



      reply	other threads:[~2012-05-28  5:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-26 19:45 The grand indentation unification project Daniel Hackney
2012-05-26 20:05 ` Glenn Morris
2012-05-27  9:28   ` Juri Linkov
2012-05-27 14:42   ` Daniel Hackney
2012-05-27 17:13     ` Miles Bader
2012-05-27 17:32       ` Daniel Hackney
2012-05-28  5:12         ` Stefan Monnier [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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=jwvzk8sucaf.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=dan@haxney.org \
    --cc=emacs-devel@gnu.org \
    --cc=miles@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).