From: Xavier Maillard <xma@gnu.org>
To: "yinglcs@gmail.com" <yinglcs@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: setting up filecache and ido
Date: Tue, 4 Nov 2008 00:25:07 +0100 [thread overview]
Message-ID: <200811032325.mA3NP7g9009128@zogzog.maillard.mobi> (raw)
In-Reply-To: <5915a45f-a1f3-4a2d-8489-d17f317eff9f@c22g2000prc.googlegroups.com> (yinglcs@gmail.com)
Hi,
I am trying to following this:
http://sachachua.com/wp/2008/07/27/eclipse-to-emacs-navigating-your-source-tree/#comment-103149
to setup my emacs with etag.
But when I include the following in my emacs.
emacs goes up to 100% cpu for > 5 minutes. Can you please tell me how
can I fix my problem?
Caching a very big directory can take time. Did you define the
base directory ? Do you use te find or locate command to cache
the directory ?
Xavier
--
http://www.gnu.org
http://www.april.org
http://www.lolica.org
prev parent reply other threads:[~2008-11-03 23:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-03 7:12 setting up filecache and ido yinglcs
2008-11-03 23:25 ` Xavier Maillard [this message]
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=200811032325.mA3NP7g9009128@zogzog.maillard.mobi \
--to=xma@gnu.org \
--cc=help-gnu-emacs@gnu.org \
--cc=yinglcs@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.
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).