From: Jason Rumney <jasonr@f2s.com>
To: bug-gnu-emacs@gnu.org
Subject: bug#5833: 23.1.94; Opening files on network shares on w32 is slow
Date: Tue, 06 Apr 2010 08:12:22 +0800 [thread overview]
Message-ID: <4BBA7C66.4090904@f2s.com> (raw)
In-Reply-To: <jwvsk791wxr.fsf-monnier+emacs@gnu.org>
On 06/04/2010 04:15, Stefan Monnier wrote:
>>> (setq locate-dominating-stop-dir-regexp "")
>>>
>> That maybe shaves off half a second.
>>
> Hmm... odd. That seemed like a pretty good guess
> (locate-dominating-file tends to suffer from such performance problems
> in some cases, and vc-handled-backends is one user of this function,
> and dir-locals is another, so setting locate-dominating-stop-dir-regexp
> should really kill it off).
>
I think it odd that it shaved time off rather than made things much
worse. One of the reasons for this variable is that when Windows tries
to locate all the siblings of //machine, and in some cases
//machine/share (where the user only has access to some shares), the
process takes a long time. Perhaps the original value is incorrect?
next prev parent reply other threads:[~2010-04-06 0:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-03 21:16 bug#5833: 23.1.94; Opening files on network shares on w32 is slow Mathias Dahl
2010-04-04 6:00 ` Eli Zaretskii
2010-04-05 11:35 ` Mathias Dahl
2010-04-05 12:33 ` Eli Zaretskii
2010-04-05 18:15 ` Mathias Dahl
2010-04-05 20:15 ` Stefan Monnier
2010-04-05 21:03 ` Mathias Dahl
2010-04-06 0:12 ` Jason Rumney [this message]
2010-04-06 0:46 ` Stefan Monnier
2010-04-05 21:58 ` Eli Zaretskii
2010-04-06 7:12 ` Mathias Dahl
2010-04-06 8:15 ` martin rudalics
2010-04-06 18:16 ` Eli Zaretskii
2010-04-07 2:53 ` Eli Zaretskii
2010-04-07 21:00 ` Mathias Dahl
2019-08-08 3:30 ` Stefan Kangas
2019-08-08 13:21 ` Eli Zaretskii
2019-08-23 17:36 ` Stefan Kangas
2019-08-23 19:27 ` Eli Zaretskii
2019-08-24 8:46 ` Mathias Dahl
2019-08-24 10:13 ` Eli Zaretskii
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=4BBA7C66.4090904@f2s.com \
--to=jasonr@f2s.com \
--cc=bug-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.