From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: emacs-devel@gnu.org
Subject: Re: Slow Info startup
Date: Wed, 30 Nov 2005 12:19:44 +0900 [thread overview]
Message-ID: <b4m1x0yhlf3.fsf@jpl.org> (raw)
In-Reply-To: 878xv6zwqa.fsf@stupidchicken.com
>>>>> In <878xv6zwqa.fsf@stupidchicken.com> Chong Yidong wrote:
> Katsumi Yamaoka <yamaoka@jpl.org> writes:
>> I have several Info directories specified to Info-directory-list
>> and there are a lot of entries in those dir files. Recently, I
>> found it takes a long time to start up Info. It is caused by
>> the change of Info-fontify-node made at 2005-11-25. Is there a
>> way to make it fast besides reducing Info-directory-list?
> The change was to correctly fontify Info buffers opened with
> Info-on-current-buffer. If we are willing to sacrifice a little
> correctness, there is one change that can speed things up. See the
> attached patch.
Thanks. I tried it and confirmed it makes the Info start fast
as before.
> The side-effect of this is that Info will fontify
> incorrectly in one corner case. This happens when you call
> Info-on-current-buffer on a file named (e.g.) "elisp" outside of
> Info-directory list, or a non-file buffer named "elisp". When you
> browse around, your Info history will be recorded as though you are
> visiting the real "elisp" info file, at /usr/share/info/elisp or
> wherever. If you later visit the "real" info file, those links will
> be fontified as "previously visited" links. Maybe that's an
> acceptable situation, however.
It seems ok if those "elisp"s are the same, if anything, that's
acceptable on me.
next prev parent reply other threads:[~2005-11-30 3:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-30 1:40 Slow Info startup Katsumi Yamaoka
2005-11-30 2:38 ` Chong Yidong
2005-11-30 2:41 ` Chong Yidong
2005-11-30 2:48 ` Juri Linkov
2005-11-30 3:19 ` Katsumi Yamaoka [this message]
2005-12-01 6:05 ` Richard M. Stallman
2005-12-01 21:47 ` Juri Linkov
2005-12-01 22:46 ` Chong Yidong
2005-12-02 0:03 ` Juri Linkov
2005-12-02 18:21 ` Richard M. Stallman
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=b4m1x0yhlf3.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=emacs-devel@gnu.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.