files.el: Once again impossible to turn off dir-settings

["T.V. Raman" <tv.raman.tv@gmail.com>]

Stefane, --yes, /homee/user is nfs mounted -- and accessing
non-existent directories in /home causes a network access. This
means that         when emacs  goes hunting in /home, it triggers
a huge number of filer accesses. 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.

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.

-- 
Best Regards,
--raman


Email:  raman@users.sf.net
WWW:    http://emacspeak.sf.net/raman/
AIM:    emacspeak       GTalk: tv.raman.tv@gmail.com
PGP:    http://emacspeak.sf.net/raman/raman-almaden.asc
Google: tv+raman
IRC:    irc://irc.freenode.net/#emacs


On 11/25/08, Stefan Monnier <monnier@iro.umontreal.ca> wrote:
>> The slowness --- at least as I observe at my end, has not been
>> fixed.
>> In the caase of vc-backends, I'm able to avoid global crawls
>> across NFS filesystems by setting
>> ;;; vc speed up:
>
>> (setq vc-ignore-dir-regexp
>> "\\`\\([\\/][\\/]\\|/net/\\|/home/\\|/afs/\\)\\'")
>> Notice the addition of /home above  -- in my case /home is nfs
>> mounted.
>
> NFS mounting as such is normally not a problem.  So could you explain
> exactly how is /home mounted?  Is it an autofs mount?  Do accesses to
> /home/foobar automatically trigger access to some network server (even
> if /home/foobar doesn't actually exist)?
>
>> I strongly urge you to reconsider forcing all users to  take the
>> hit of searching for project settings.
>
>> For now, I've defadviced hack-dir-local-variables like so:
>> (defadvice hack-dir-local-variables (around fix-slowness pre act comp)
>>   "Restore democracy, restore speed"
>> nil)
>
> There's locate-dominating-stop-dir-regexp (which will apply both to VC
> and to dir-settings).
>
>
>         Stefan
>