From: W. Greenhouse <wgreenhouse-sGOZH3hwPm2sTnJN9+BGXg@public.gmane.org>
To: help-gnu-emacs-mXXj517/zsQ@public.gmane.org
Subject: Re: emacs causing automount error
Date: Tue, 11 Feb 2014 16:46:15 +0000 [thread overview]
Message-ID: <87txc5lhrc.fsf@motoko.kusanagi> (raw)
In-Reply-To: 38b946ba-8d2d-49ee-9d04-6f5e72d44a9c@googlegroups.com
Patrick <patrick.brem87-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> Hello,
>
> I am using emacs on several machines, and now my system administrator
> told me that on one machine his log files are filled up with this
>
> Feb 10 14:38:46 xx automount[3394]: key ".bzr" not found in map source(s).
> Feb 10 14:38:46 xx automount[3394]: key ".git" not found in map source(s).
> Feb 10 14:38:46 xx automount[3394]: key ".hg" not found in map source(s).
> Feb 10 14:38:46 xx automount[3394]: key "_MTN" not found in map source(s).
> Feb 10 14:38:46 xx automount[3394]: key "{arch}" not found in map source(s).
>
> Comparing the timestamps, this happens everytime I start emacs. Is
> anyone familiar with this problem or can point me to where I can stop
> emacs from trying to access all these inexisting keys on startup?
This looks like evidence of vc-mode trying to check if the current
directory is under version control. The nuclear option would be to
(setq vc-handled-backends nil), thus entirely disabling all attempts to
tell if any file/directory is under version control.
next prev parent reply other threads:[~2014-02-11 16:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-11 9:50 emacs causing automount error Patrick
2014-02-11 14:56 ` Michael Albinus
2014-02-11 15:03 ` Andy Moreton
2014-02-11 16:46 ` W. Greenhouse [this message]
2014-02-11 16:56 ` Glenn Morris
2014-02-11 22:26 ` Stefan Monnier
[not found] ` <mailman.14783.1392137889.10748.help-gnu-emacs@gnu.org>
2014-02-11 21:14 ` patrick.brem87
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=87txc5lhrc.fsf@motoko.kusanagi \
--to=wgreenhouse-sgozh3hwpm2stnjn9+bgxg@public.gmane.org \
--cc=help-gnu-emacs-mXXj517/zsQ@public.gmane.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.