From: David Kastrup <dak@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: bruce.connor.am@gmail.com, emacs-devel <emacs-devel@gnu.org>
Subject: Re: On tabs and spaces
Date: Thu, 15 Jan 2015 12:42:01 +0100 [thread overview]
Message-ID: <87wq4oe0dy.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <54B799B7.6040004@yandex.ru> (Dmitry Gutov's message of "Thu, 15 Jan 2015 13:43:03 +0300")
Dmitry Gutov <dgutov@yandex.ru> writes:
> On 01/15/2015 01:26 PM, David Kastrup wrote:
>
>> Once you factor the time of C-x v g into the equation, the 5.5s of
>> difference are not all that impressive. On my computer, previous to
>> version 2.1 we were talking about about 5 _minutes_ of runtime.
>
> Still inconvenient, though. And maybe we also care about the
> developers with older versions of Git, for now.
The developers with older versions of Git are much less likely to even
notice the difference since the older versions spend the bulk of the
runtime elsewhere. So the 5.5s of difference are likely still about
5.5s of difference for the old versions.
> The improvement is impressive, to be sure.
>
>> Emacs
>> doesn't use -w by default when doing C-x v g either IIRC. Getting it in
>> there is somewhat cumbersome.
>
> Using it by default would be a trivial change.
But not likely appropriate for some applications, and not likely matched
by the behavior of other version control systems in VC. Still, it's a
bit too far out of reach from inside Emacs.
> And with http://debbugs.gnu.org/17945, vc-annotate will be more
> customizable.
Not yet looked at it.
--
David Kastrup
next prev parent reply other threads:[~2015-01-15 11:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 23:15 On tabs and spaces Artur Malabarba
2015-01-14 23:22 ` Dmitry Gutov
2015-01-15 1:01 ` Artur Malabarba
2015-01-15 9:57 ` David Kastrup
2015-01-15 10:17 ` Dmitry Gutov
2015-01-15 10:26 ` David Kastrup
2015-01-15 10:43 ` Dmitry Gutov
2015-01-15 11:42 ` David Kastrup [this message]
2015-01-16 7:23 ` Stephen Leake
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=87wq4oe0dy.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=bruce.connor.am@gmail.com \
--cc=dgutov@yandex.ru \
--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.