From: "Eli Zaretskii" <eliz@elta.co.il>
Cc: emacs-devel@gnu.org
Subject: Re: info-lookup delay on missing file
Date: Thu, 28 Aug 2003 09:13:14 +0200 [thread overview]
Message-ID: <4331-Thu28Aug2003091313+0300-eliz@elta.co.il> (raw)
In-Reply-To: <874r02myov.fsf@zip.com.au> (message from Kevin Ryde on Thu, 28 Aug 2003 10:08:00 +1000)
> From: Kevin Ryde <user42@zip.com.au>
> Date: Thu, 28 Aug 2003 10:08:00 +1000
>
> 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.
What happens if _none_ of the files in info-lookup-alist exist? Does
the user get any messages with your change, or will Emacs simply do
nothing visible (quietly)? If the latter, I'm not sure the proposed
behavior is a good idea.
Btw, one alternative is to be less talkative, but not to omit the
information altogether, either: put the message into *Messages*, but
don't display it and don't sit-for.
next prev parent reply other threads:[~2003-08-28 7:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-28 0:08 info-lookup delay on missing file Kevin Ryde
2003-08-28 7:13 ` Eli Zaretskii [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4331-Thu28Aug2003091313+0300-eliz@elta.co.il \
--to=eliz@elta.co.il \
--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.