From: Paul Eggert <eggert@cs.ucla.edu>
To: Dmitry Gutov <dgutov@yandex.ru>, Eli Zaretskii <eliz@gnu.org>,
bruce.connor.am@gmail.com, dak@gnu.org, emacs-devel@gnu.org
Subject: Re: Should we have a commit size guideline?
Date: Tue, 15 Dec 2015 17:00:07 -0800 [thread overview]
Message-ID: <5670B797.5080200@cs.ucla.edu> (raw)
In-Reply-To: <5670AF1D.1090803@yandex.ru>
Dmitry Gutov wrote:
> Emacs doesn't change tabs to spaces if the indentation level of the line
> hasn't changed.
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). In this case Emacs changes tabs to spaces,
assuming the .dir-locals.el settings already mentioned.
> we've always considered tabs-to-spaces changes near some actual
> changed code to be okay.
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.
It is a bit of an annoyance, that's all. Obviously there are workarounds. It's
not something I'd bother writing about, but I'm sympathetic to those bothered
enough to write.
next prev parent reply other threads:[~2015-12-16 1:00 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 [this message]
2015-12-16 1:19 ` indent-tabs-mode setting in Emacs's dir-locals.el Dmitry Gutov
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=5670B797.5080200@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=bruce.connor.am@gmail.com \
--cc=dak@gnu.org \
--cc=dgutov@yandex.ru \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.