unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Augusto Stoffel <arstoffel@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, dalanicolai@gmail.com, emacs-devel@gnu.org
Subject: Re: Search multiple Info-buffers at once with Info-occur function
Date: Sat, 29 May 2021 10:14:35 -0400	[thread overview]
Message-ID: <jwvzgwdd3zr.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <878s3x4rju.fsf@gmail.com> (Augusto Stoffel's message of "Sat, 29 May 2021 15:07:17 +0200")

>> Are you sure the facilities in info-look.el aren't a better starting
>> point (or maybe even a solution) for the problems you have in mind?
>
> Ah, I wasn't aware of this.  It's pretty much what I had in mind.
>
> 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.

Maybe info-look.el can be extended with:
- a way for the user to specify (even interactively) a particular set of
  of manuals to use in a particular buffer.
- a heuristic to find symbols in manuals without any manually curated
  description of what constitutes a symbol.

Maybe that heuristic could then be "upstreamed" into a formally defined
and documented Texinfo convention that future manual authors would be
expected to follow?


        Stefan




  parent reply	other threads:[~2021-05-29 14:14 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
2021-05-29 14:06                           ` Eli Zaretskii
2021-05-29 14:14                       ` Stefan Monnier [this message]
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

  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=jwvzgwdd3zr.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=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 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).