From: Juri Linkov <juri@jurta.org>
Cc: yamaoka@jpl.org, emacs-devel@gnu.org
Subject: Re: Slow Info startup
Date: Wed, 30 Nov 2005 04:48:47 +0200 [thread overview]
Message-ID: <87y836j09n.fsf@jurta.org> (raw)
In-Reply-To: <878xv6zwqa.fsf@stupidchicken.com> (Chong Yidong's message of "Tue, 29 Nov 2005 21:38:05 -0500")
> 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.
It seems this patch just reverts your changes in that part.
> 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.
I think this is not a big issue. Another case where it might not
fontify correctly is when the user changes Info-directory-list so
xrefs to the manuals with the same name are fontified as xrefs to
the same manual. OTOH, with the old code in info.el, the user could
move the same manual to another directory in Info-directory-list and
still be able to see xrefs to the moved manual fontified correctly.
So the old "manual-name-based" code (instead of the new "file-name-based")
is not absolutely incorrect, and is much faster.
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2005-11-30 2:48 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 [this message]
2005-11-30 3:19 ` Katsumi Yamaoka
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
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=87y836j09n.fsf@jurta.org \
--to=juri@jurta.org \
--cc=emacs-devel@gnu.org \
--cc=yamaoka@jpl.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).