all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Augusto Stoffel <arstoffel@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: dalanicolai@gmail.com, emacs-devel@gnu.org
Subject: Re: Search multiple Info-buffers at once with Info-occur function
Date: Sat, 29 May 2021 15:48:03 +0200	[thread overview]
Message-ID: <874kel4pnw.fsf@gmail.com> (raw)
In-Reply-To: <83mtsd653j.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 29 May 2021 16:29:20 +0300")

On Sat, 29 May 2021 at 16:29, Eli Zaretskii <eliz@gnu.org> wrote:

>> The only downside of info-look (and I guess this is inherent to the info
>> format, or to long-form documentation is general) is that you can't just
>> pick a random collection of manuals to search for symbols.  Instead,
>> there's a manually curated list of modes (via
>> `info-lookup-maybe-add-help') with recipes as to what constitutes a
>> symbol in that manual.
>
> That's true, but how else can Emacs possibly know which manual(s)
> is/are relevant to a random symbol or major mode?  Eventually, you
> must have some DB of data that connects these dots, and info-look.el
> provides the infrastructure to maintain and extend such a DB.  Right?
> Or am I missing something?

That's inevitable, of course.  The "evdocs" package I just submitted
here will just ask you which manual(s) to search; alternatively, you can
set a variable, say in a major mode hook, to avoid that question.

But what I find a bit annoying is something else, namely the fact that
info-look.el defines a bunch of regexps to decide what constitutes a
symbol in each manual.  So you can't just say "oh, by the way, please
include also the manual of the Dash library when I'm in Elisp mode"
(unless there's something else I'm missing...).



  reply	other threads:[~2021-05-29 13:48 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-22 22:17 Search multiple Info-buffers at once with Info-occur function dalanicolai
2021-05-23  7:02 ` Eli Zaretskii
2021-05-23  8:39   ` dalanicolai
2021-05-23  8:56     ` dalanicolai
2021-05-23  9:32       ` Eli Zaretskii
2021-05-24  8:37         ` dalanicolai
2021-05-24  8:51           ` Eli Zaretskii
2021-05-25 14:12             ` dalanicolai
2021-05-25 14:24               ` dalanicolai
2021-05-29 12:07                 ` Augusto Stoffel
2021-05-29 12:15                   ` Eli Zaretskii
2021-05-29 13:07                     ` Augusto Stoffel
2021-05-29 13:29                       ` Eli Zaretskii
2021-05-29 13:48                         ` Augusto Stoffel [this message]
2021-05-29 14:06                           ` Eli Zaretskii
2021-05-29 14:14                       ` Stefan Monnier
2021-05-29 14:40                         ` Eli Zaretskii
2021-05-29 12:17                   ` dalanicolai
2021-05-29 12:37                     ` dalanicolai
2021-05-23  9:29     ` Eli Zaretskii
2021-05-23 20:47       ` [External] : " Drew Adams
2021-05-24  8:46         ` dalanicolai
2021-05-24 17:55           ` Drew Adams
2021-05-25 12:29             ` dalanicolai
2021-05-25 13:58               ` Drew Adams
2021-05-25 14:33                 ` dalanicolai
2021-05-23 15:42     ` Measuring execution time of a function Stefan Monnier
2021-05-24  8:35       ` dalanicolai

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=874kel4pnw.fsf@gmail.com \
    --to=arstoffel@gmail.com \
    --cc=dalanicolai@gmail.com \
    --cc=eliz@gnu.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.