From: Drew Adams <drew.adams@oracle.com>
To: Juri Linkov <juri@linkov.net>, Lars Ingebrigtsen <larsi@gnus.org>
Cc: emacs-devel@gnu.org
Subject: RE: master 2a7488d: Add support for displaying short documentation for function groups
Date: Tue, 13 Oct 2020 13:35:12 -0700 (PDT) [thread overview]
Message-ID: <b8510b0d-afd8-4020-a132-b9457f70bb03@default> (raw)
In-Reply-To: <87eem2ey3n.fsf@mail.linkov.net>
> I have pondered a year ago about doing something like this,
> but based on Info and/or HTML, i.e. to generate Info nodes with
> functions listed by groups in separate nodes (possibly using HTML format),
> so e.g. going to (info "(shortdoc) Buffer")
> could display an Info node with a menu of related functions,
> where nodes could be navigated using Info keys.
> Does this make sense?
Doesn't `Info-virtual-index' already do that?
E.g. `I buffer' gives you an index with just
the index entries that match "buffer".
Maybe you can state the difference between that
command and what you have in mind, to clarify.
next prev parent reply other threads:[~2020-10-13 20:35 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201011035127.7723.3256@vcs0.savannah.gnu.org>
[not found] ` <20201011035128.E3FD320667@vcs0.savannah.gnu.org>
2020-10-11 3:55 ` master 2a7488d: Add support for displaying short documentation for function groups Lars Ingebrigtsen
2020-10-11 13:49 ` Eli Zaretskii
2020-10-11 21:47 ` Lars Ingebrigtsen
2020-10-11 23:38 ` Drew Adams
2020-10-12 8:05 ` Gregory Heytings via Emacs development discussions.
2020-10-12 16:20 ` Drew Adams
2020-10-12 16:50 ` Gregory Heytings via Emacs development discussions.
2020-10-12 17:29 ` Drew Adams
2020-10-13 20:05 ` Juri Linkov
2020-10-13 20:35 ` Drew Adams [this message]
2020-10-14 7:48 ` Juri Linkov
2020-10-13 20:55 ` T.V Raman
2020-10-14 7:52 ` Juri Linkov
2020-10-14 14:41 ` T.V Raman
2020-10-14 4:12 ` Lars Ingebrigtsen
2020-10-14 7:59 ` Juri Linkov
2020-10-15 6:43 ` Lars Ingebrigtsen
2020-10-15 12:24 ` Stefan Monnier
2020-10-18 20:12 ` Juri Linkov
2020-10-19 3:47 ` Richard Stallman
2020-10-19 8:05 ` Juri Linkov
2020-10-23 20:24 ` Stefan Kangas
2020-10-24 19:59 ` Lars Ingebrigtsen
2020-10-24 23:51 ` Stefan Kangas
2020-10-25 13:04 ` Lars Ingebrigtsen
2020-10-27 13:48 ` Basil L. Contovounesios
2020-10-27 14:33 ` Stefan Kangas
2020-10-27 15:43 ` Basil L. Contovounesios
2020-10-27 17:33 ` Lars Ingebrigtsen
2020-10-27 22:02 ` Stefan Kangas
2020-10-28 8:20 ` Mattias Engdegård
2020-10-28 13:50 ` Stefan Kangas
2020-10-28 11:04 ` Lars Ingebrigtsen
[not found] ` <CADwFkmnXuyh2cAddLtgTNmsSv8av3o9qk98CVcTAzq6B8Lrpkw@mail.gmail.com>
[not found] ` <87blgknjze.fsf@gnus.org>
2020-10-30 11:58 ` Stefan Kangas
2020-10-30 12:05 ` Lars Ingebrigtsen
2020-10-30 12:27 ` Stefan Kangas
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=b8510b0d-afd8-4020-a132-b9457f70bb03@default \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
--cc=larsi@gnus.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).