From: JD Smith <jdtsmith@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>,
Karsten Rodenacker <karsten.rodenacker@helmholtz-muenchen.de>
Cc: emacs-pretest-bug@gnu.org
Subject: Re: Extremely slow (buggy?) function
Date: Thu, 28 Feb 2008 13:59:44 -0500 [thread overview]
Message-ID: <9892E1A6-DEDB-428D-BC18-45F4977728BB@gmail.com> (raw)
In-Reply-To: <jwv3ard3qjk.fsf-monnier+emacs@gnu.org>
On Feb 28, 2008, at 1:07 PM, Stefan Monnier wrote:
> Can you take a look at this report?
> It seems to be a performance problem in idlwave.
>> From: Karsten Rodenacker <karsten.rodenacker@helmholtz-muenchen.de>
>> Date: 28 February 2008 15:22:16 GMT
>> To: aquamacs-bugs@aquamacs.org
>> Subject: [Aquamacs-bugs] Extremely slow (buggy?) function
>>
>> Enter your bug report here.
>>
>> After starting and using idlwave module emacs becomes extremely slow
>> and unresponsive during the message:
>>
>> Loading and normalizing library catalogs in idle time...done
This is to be expected when you have a large (IDL) search path, or
(especially) one which includes slow network shares. During this
message, IDLWAVE is searching the path for `.idlwave_catalog' files,
and loading them. Try setting `idlwave-use-library-catalogs' to nil
to see if the problem goes away. If so, it probably relates to the
size of the search path (held in `idlwave-path-alist', which is
gathered from the IDL shell, or explicitly set in `idlwave-library-
path'), or to a slow network share. Another option would be to
explicitly set idlwave-library-path to a smaller file tree.
>> This behaviour appeared with Version 1.3
I'm not aware of any recent changes in behavior for library catalogs.
JD
prev parent reply other threads:[~2008-02-28 18:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <40B6A9D4-9FE0-4C25-B9A7-0422C46D2E82@helmholtz-muenchen.de>
2008-02-28 15:33 ` Fwd: Extremely slow (buggy?) function David Reitter
2008-02-28 18:07 ` Stefan Monnier
2008-02-28 18:59 ` JD Smith [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9892E1A6-DEDB-428D-BC18-45F4977728BB@gmail.com \
--to=jdtsmith@gmail.com \
--cc=emacs-pretest-bug@gnu.org \
--cc=karsten.rodenacker@helmholtz-muenchen.de \
--cc=monnier@iro.umontreal.ca \
/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.