From: Robert Thorpe <rt@robertthorpeconsulting.com>
To: Emanuel Berg <embe8573@student.uu.se>
Cc: help-gnu-emacs@gnu.org
Subject: Re: removing white space highlight
Date: Sat, 27 Feb 2016 20:54:10 +0000 [thread overview]
Message-ID: <87ziul98nh.fsf@robertthorpeconsulting.com> (raw)
In-Reply-To: <87ziuokv2g.fsf@debian.uxu> (message from Emanuel Berg on Fri, 26 Feb 2016 04:29:59 +0100)
Emanuel Berg <embe8573@student.uu.se> writes:
> This discussion for example is perhaps closing in on
> that :)
Yes. I'll have one last go at it though.
> Robert Thorpe <rt@robertthorpeconsulting.com> writes:
>
>>> I'll be like that once for every file.
>>
>> Yes, for decades.
>
> Are there so really so many files that are left
> untouched for so long?
Not files, no, I'm talking about *lines*.
Perhaps an example will clarify things.... Here is the (fictional)
output of "svn annotate" on a fictional file:
$ svn blame nasty.c
103 sally /* important_parameter should be */
103 sally /* set for modern memory sizes. */
115 harry int important_parameter = 42;
103 sally
For each line the revision is given when the file was changed, and the
person who changed it. You can get this with C-x v g from Emacs.
Let's say that version 115 was a reasonably recent. In that case it's
likely that Harry set tuned important_parameter for current memory sizes
at that time.
But, what if Harry just deleted some extraneous whitespace from the end
of the line? In that case we can't be sure when important_parameter was
last set. It may be very old.
Removing the whitespace change we may have the situation:
$ svn blame -x -b nasty.c
103 sally /* important_parameter should be */
103 sally /* set for modern memory sizes. */
24 terry int important_parameter = 42;
103 sally
This shows that the last actual change was in revision 24, which was
years ago.
In the Subversion manual it explicitly mentions this situation.
Subversion has a command to deal with it, "-x -b", which ignores
whitespace changes. Not all version controls systems have that. It's
also not very well known and tools that use the VC system (GUIs and
Editors) may not use it. Stefan mentions that Git has a way of doing
this too.
When all the tools deal with this situation well then I'll be happy with
indiscriminate whitespace changes, but we're not at that point yet.
BR,
Robert Thorpe
next prev parent reply other threads:[~2016-02-27 20:54 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 10:06 removing white space highlight Luca Ferrari
2016-02-18 10:19 ` Gian Uberto Lauri
2016-02-18 10:54 ` Luca Ferrari
2016-02-18 10:30 ` tomas
2016-02-18 13:34 ` Luca Ferrari
2016-02-18 13:17 ` tomas
2016-02-18 14:37 ` Luca Ferrari
2016-02-18 14:15 ` tomas
2016-02-18 16:08 ` Luca Ferrari
2016-02-19 0:23 ` Emanuel Berg
2016-02-19 1:05 ` Drew Adams
2016-02-19 16:02 ` Marcin Borkowski
2016-02-19 20:43 ` Emanuel Berg
2016-02-19 20:50 ` Marcin Borkowski
2016-02-20 0:30 ` Emanuel Berg
2016-02-20 19:08 ` Bob Proulx
2016-02-21 0:32 ` Emanuel Berg
2016-02-21 1:34 ` Bob Proulx
2016-02-21 1:48 ` Emanuel Berg
2016-02-21 3:27 ` Robert Thorpe
2016-02-21 3:31 ` Emanuel Berg
2016-02-21 5:00 ` Marcin Borkowski
2016-02-21 6:10 ` Emanuel Berg
2016-02-21 11:48 ` tomas
2016-02-21 17:13 ` Emanuel Berg
2016-02-23 0:33 ` Robert Thorpe
2016-02-23 0:41 ` Emanuel Berg
2016-02-24 0:44 ` Robert Thorpe
2016-02-24 1:41 ` Emanuel Berg
2016-02-24 20:38 ` Robert Thorpe
2016-02-25 0:10 ` Emanuel Berg
2016-02-25 8:47 ` Luca Ferrari
2016-02-25 9:29 ` Christian Kruse
2016-02-25 19:58 ` Robert Thorpe
2016-02-25 20:10 ` vc-region-history promotion (was: removing white space highlight) Stefan Monnier
2016-02-25 22:15 ` removing white space highlight Emanuel Berg
2016-02-25 22:41 ` Robert Thorpe
2016-02-26 0:02 ` Emanuel Berg
2016-02-26 2:58 ` Robert Thorpe
2016-02-26 3:29 ` Emanuel Berg
2016-02-26 6:08 ` Bob Proulx
2016-02-26 19:48 ` Emanuel Berg
2016-02-27 20:54 ` Robert Thorpe [this message]
2016-02-28 2:43 ` Emanuel Berg
2016-02-28 18:09 ` Robert Thorpe
2016-02-29 0:52 ` Emanuel Berg
2016-02-29 2:43 ` Robert Thorpe
2016-02-22 14:05 ` Luca Ferrari
2016-02-23 0:13 ` Emanuel Berg
2016-02-23 0:34 ` Robert Thorpe
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=87ziul98nh.fsf@robertthorpeconsulting.com \
--to=rt@robertthorpeconsulting.com \
--cc=embe8573@student.uu.se \
--cc=help-gnu-emacs@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.