From: Kevin Ryde <user42@zip.com.au>
Subject: info-lookup delay on missing file
Date: Thu, 28 Aug 2003 10:08:00 +1000 [thread overview]
Message-ID: <874r02myov.fsf@zip.com.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1344 bytes --]
When an info file specified in info-lookup-alist doesn't exit,
info-lookup has a message and sit-for every time it goes across that
file in doing a lookup.
For instance in sh-mode, diff.info is after coreutils.info. If you
don't have coreutils.info and you try "C-h C-i diff" there's a message
and delay
Cannot access Info node (coreutils)Index
every time before going on to bring up the diff manual. During the
delay an unrelated index is shown in the info window, which I also
think is quite disconcerting.
I'd like to propose quietly ignoring such inaccessible files,
* info-look.el (info-lookup): Don't sit-for and message on
inaccessible info file. This was done on every lookup going past that
file's entry and was too annoying. Leave it to happen just once on
building the cache.
There's still a message while first loading up info-lookup-cache,
ie. the first lookup in a mode, hopefully that's enough of a warning.
I struck this when appending further manuals to the c-mode setups. I
don't have a termcap.info for that entry in the default setups and so
got a delay on every lookup of one of my additions.
Obviously it's not too hard to delete info-lookup-alist bits for
things you doesn't have, but it seems to me friendlier to give just
one warning and thereafter ignore missing stuff.
[-- Attachment #2: info-look.el.message.diff --]
[-- Type: text/plain, Size: 656 bytes --]
*** info-look.el.~1.34.~ Thu Jan 1 10:00:01 1970
--- info-look.el Thu Aug 21 14:53:47 2003
*************** (defun info-lookup (topic item mode)
*** 351,360 ****
(progn
(Info-goto-node node)
(setq doc-found t))
! (error
! (message "Cannot access Info node %s" node)
! (sit-for 1)
! nil))
(condition-case nil
(progn
;; Don't use Info-menu, it forces case-fold-search to t
--- 351,357 ----
(progn
(Info-goto-node node)
(setq doc-found t))
! (error nil))
(condition-case nil
(progn
;; Don't use Info-menu, it forces case-fold-search to t
[-- Attachment #3: Type: text/plain, Size: 142 bytes --]
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
next reply other threads:[~2003-08-28 0:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-28 0:08 Kevin Ryde [this message]
2003-08-28 7:13 ` info-lookup delay on missing file Eli Zaretskii
2003-08-29 22:48 ` Kevin Ryde
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=874r02myov.fsf@zip.com.au \
--to=user42@zip.com.au \
/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).