unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "T.V. Raman" <tv.raman.tv@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: files.el: Once again impossible to turn off dir-settings
Date: Wed, 26 Nov 2008 09:37:01 -0500	[thread overview]
Message-ID: <jwvprki4l4x.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <5f0ff9220811252033t11d9a8cfied2d69075827bd7c@mail.gmail.com> (T. V. Raman's message of "Tue, 25 Nov 2008 20:33:11 -0800")

> Stefan, --yes, /homee/user is nfs mounted -- and accessing
> non-existent directories in /home causes a network access.

So if I access /home/<foo>, which remote machine is being accessed?

> means that         when emacs  goes hunting in /home, it triggers
> a huge number of filer accesses.

In my experience, the actual number of accesses is not important.
What matters is whether one of them triggers access to a nonexistent
remote machine.  E.g trying to find /net/.dir-settings.el can cause the
autofs file system to try and contact the ".dir-settings.el" server
which doesn't exist (if you get lucky, you immediately get an error,
but you may also end up waiting for a timeout, and in any case you end
up waiting for DNS resolution, which can take a few seconds).

> I wasn't aware of the other regexp -- I'll use that.  But for the
> foreseeable future I expect to disable dir-setings -- at least until
> there is a project using it.

Sounds reasonable.

> I use Emacs for many things, including writing code, -- not
> exclusively for writing code; and for that use case, it's
> important that emacs not always go trawling around for project settings.

Dir settings are not only for "programming projects".  They can be used
for anything, just like file variables (which I actually tend to use
more in non-programming files).  Also as long as you don't have any
.dir-settings.el files, then the only difference between activating and
deactivating the feature is the time taken to to look up those files,
but since VC looks up several similar files anyway, the slow down should
be lost in the noise (unless you set vc-ignore-dir-regexp to a value
different from locate-dominating-stop-dir-regexp, as you've seen).


        Stefan




  reply	other threads:[~2008-11-26 14:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-25 14:13 files.el: Once again impossible to turn off dir-settings T.V. Raman
2008-11-25 15:30 ` Stefan Monnier
2008-11-25 19:00   ` T.V. Raman
2008-11-25 21:48     ` Stefan Monnier
2008-11-25 22:42       ` Chong Yidong
2008-11-26  1:37         ` Stefan Monnier
2008-11-26  4:33       ` T.V. Raman
2008-11-26 14:37         ` Stefan Monnier [this message]
2008-11-29  3:46     ` Miles Bader
2008-11-25 16:04 ` Juri Linkov
2008-11-25 19:03   ` T.V. Raman
2008-11-25 20:02   ` Tom Tromey
2008-11-25 22:19     ` T.V. Raman
2008-11-27  0:00       ` Juri Linkov

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=jwvprki4l4x.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=tv.raman.tv@gmail.com \
    /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).