From: Jambunathan K <kjambunathan@gmail.com>
To: Nikolai Weibull <now@bitwi.se>
Cc: Eli Zaretskii <eliz@gnu.org>, flat0103@gmail.com, emacs-devel@gnu.org
Subject: Re: slow opening of files in git directories in windows
Date: Thu, 27 Oct 2011 16:33:44 +0530 [thread overview]
Message-ID: <8162ja8zn3.fsf@gmail.com> (raw)
In-Reply-To: <CADdV=Mvcu_4BLR2aF9bvfgFTcqi_XF+R77=z121czmNVfY_rdQ@mail.gmail.com> (Nikolai Weibull's message of "Thu, 27 Oct 2011 12:14:04 +0200")
Nikolai Weibull <now@bitwi.se> writes:
> On Thu, Oct 27, 2011 at 11:48, Eli Zaretskii <eliz@gnu.org> wrote:
>>> Date: Thu, 27 Oct 2011 08:45:28 +0200
>>> From: Nikolai Weibull <now@bitwi.se>
>>> Cc: emacs-devel@gnu.org
>>>
>>> On Thu, Oct 27, 2011 at 08:39, Nathaniel Flath <flat0103@gmail.com> wrote:
>>> > I've noticed that opening files in git repositories open fairly slowly using
>>> > the latest pretest in windows - sometimes it takes several seconds, whereas
>>> > the same file not under a repository opens instantly. What would be the
>>> > best way to track this down?
>>>
>>> It’s vc(-git) that’s causing it. It runs git a couple of times, which
>>> is slow on Windows. Unbelievably slow.
>
>> Can you tell which git commands are run when a file is visited, and
>> which are slow?
>
> Sorry, I have no insight into vc-mode, but I’m guessing that it runs
> git rev-parse --show-cdup, git status, and such command to determine
> the current status of the opened file.
If you have this
(setq vc-command-messages t)
then you can see the command that vc issues in the messages buffer.
>
>
--
next prev parent reply other threads:[~2011-10-27 11:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 6:39 slow opening of files in git directories in windows Nathaniel Flath
2011-10-27 6:45 ` Nikolai Weibull
2011-10-27 9:48 ` Eli Zaretskii
2011-10-27 10:14 ` Nikolai Weibull
2011-10-27 11:03 ` Jambunathan K [this message]
2011-10-27 11:15 ` Eli Zaretskii
2011-10-27 6:52 ` Jambunathan K
2011-10-27 7:21 ` Nikolai Weibull
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=8162ja8zn3.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=flat0103@gmail.com \
--cc=now@bitwi.se \
/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).