unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Paul Eggert <eggert@cs.ucla.edu>, Eli Zaretskii <eliz@gnu.org>,
	bruce.connor.am@gmail.com, dak@gnu.org, emacs-devel@gnu.org
Subject: indent-tabs-mode setting in Emacs's dir-locals.el
Date: Wed, 16 Dec 2015 03:19:21 +0200	[thread overview]
Message-ID: <5670BC19.6030002@yandex.ru> (raw)
In-Reply-To: <5670B797.5080200@cs.ucla.edu>

On 12/16/2015 03:00 AM, Paul Eggert wrote:

> I observe problems in this area when changing code (which changes
> indentation) and then changing it back (i.e., not undo, but make a
> further change that undoes most or all of the original change).

Indeed, that would do it.

> In this
> case Emacs changes tabs to spaces, assuming the .dir-locals.el settings
> already mentioned.

Yup. But it only makes a difference if Arthur hasn't customized 
indent-tabs-mode to nil in his Emacs already.

Having a project-wide setting, however, lets us hope that someday the 
indentation style will be uniform, and this problem won't occur anymore.

> Yes, of course.  Here, though, a two-line changed ballooned into a
> 23-line change. The first 2 lines of the ballooned change were real, and
> the other 21 lines were tabs-to-spaces only.

I usually try to undo such hunks with `diff-hl-revert-hunk'.




      reply	other threads:[~2015-12-16  1:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-15 13:48 Should we have a commit size guideline? (was: builds are getting slower?) Artur Malabarba
2015-12-15 14:23 ` Should we have a commit size guideline? David Kastrup
2015-12-16 11:12   ` Artur Malabarba
2015-12-15 16:16 ` Should we have a commit size guideline? (was: builds are getting slower?) Eli Zaretskii
2015-12-15 17:56   ` Should we have a commit size guideline? John Wiegley
2015-12-16  0:13     ` Paul Eggert
2015-12-16  0:23       ` Dmitry Gutov
2015-12-16  1:00         ` Paul Eggert
2015-12-16  1:19           ` Dmitry Gutov [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=5670BC19.6030002@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=bruce.connor.am@gmail.com \
    --cc=dak@gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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).