From: Eli Zaretskii <eliz@gnu.org>
To: John Yates <john@yates-sheets.org>
Cc: andremegafone@gmail.com, theophilusx@gmail.com, rms@gnu.org,
monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Keybinding styles
Date: Thu, 09 Sep 2021 08:39:51 +0300 [thread overview]
Message-ID: <83k0jql32w.fsf@gnu.org> (raw)
In-Reply-To: <CAJnXXojk=PDC0-WJOcjBU1XaGe4ts403xjSO+kDE1C_BtgVxaw@mail.gmail.com> (message from John Yates on Wed, 8 Sep 2021 16:37:05 -0400)
> From: John Yates <john@yates-sheets.org>
> Date: Wed, 8 Sep 2021 16:37:05 -0400
> Cc: Tim Cross <theophilusx@gmail.com>, Emacs developers <emacs-devel@gnu.org>,
> Richard Stallman <rms@gnu.org>, Stefan Monnier <monnier@iro.umontreal.ca>
>
> On Wed, Sep 8, 2021 at 8:15 AM André A. Gomes <andremegafone@gmail.com> wrote:
> First iteration:
> * Add a new Tex markup item whose required first argument
> would be a function name and whose optional second argument
> would be a key sequence.
> * Makeinfo would make both data available in the generated info
> file. A standalone info reader would display the optional second
> argument if present. The emacs info reader would lookup any
> current bindings for the function name.
>
> Second iteration:
> * Modify makeinfo to accept a table of bindings. In this case any
> optional second argument would be ignored. Instead bindings
> for a function name would be looked up in that table and included
> in the output.
I don't see a need to modify anything but info.el. A table that you
want already exists: it's the Index. We need a special-purpose index
for this: one that maps commands to keys, but Texinfo already supports
the capability of defining new types of indices. A markup for keys
also already exists. So all that's needed is to add a feature to
info.el to display a different set of keys given some state variable.
Of course, the printed manual will still show only the standard key
bindings, and so will the HTML-formatted manual we put on the Web
site.
next prev parent reply other threads:[~2021-09-09 5:39 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-03 18:00 [External] : Re: Gitlab Migration Drew Adams
2021-09-03 20:06 ` Stefan Kangas
2021-09-03 22:49 ` Stefan Monnier
2021-09-04 2:00 ` Tim Cross
2021-09-04 13:26 ` Keybinding styles (was: [External] : Re: Gitlab Migration) Stefan Monnier
2021-09-04 13:39 ` Dmitry Gutov
2021-09-04 14:25 ` Keybinding styles Stefan Monnier
2021-09-04 15:44 ` Keybinding styles (was: [External] : Re: Gitlab Migration) Yuan Fu
2021-09-04 15:50 ` Eli Zaretskii
2021-09-04 15:55 ` Drew Adams
2021-09-04 16:07 ` Yuan Fu
2021-09-04 16:19 ` Eli Zaretskii
2021-09-06 3:07 ` Richard Stallman
2021-09-06 11:28 ` Dmitry Gutov
2021-09-04 19:55 ` Keybinding styles Daniel Fleischer
2021-09-04 20:52 ` Stefan Kangas
2021-09-05 7:17 ` tomas
2021-09-04 16:09 ` Bird
2021-09-04 20:48 ` Keybinding styles (was: [External] : Re: Gitlab Migration) Tim Cross
2021-09-05 19:03 ` John Yates
2021-09-06 4:34 ` Eli Zaretskii
2021-09-07 3:16 ` Richard Stallman
2021-09-07 12:02 ` John Yates
2021-09-08 3:29 ` Richard Stallman
2021-09-08 12:15 ` Keybinding styles André A. Gomes
2021-09-08 13:18 ` Eli Zaretskii
2021-09-08 20:37 ` John Yates
2021-09-09 5:39 ` Eli Zaretskii [this message]
2021-09-15 13:40 ` André A. Gomes
2021-09-15 14:26 ` Stefan Kangas
2021-09-15 15:36 ` Eli Zaretskii
2021-09-15 20:15 ` Richard Stallman
2021-09-15 21:29 ` Alexandre Garreau
2021-09-16 5:20 ` Eli Zaretskii
2021-09-16 5:00 ` Eli Zaretskii
2021-09-09 3:09 ` Richard Stallman
2021-09-04 16:05 ` [External] : Re: Gitlab Migration Stefan Kangas
2021-09-04 2:20 ` Drew Adams
2021-09-04 13:14 ` Stefan Monnier
2021-09-04 14:58 ` Drew Adams
2021-09-04 16:10 ` Stefan Monnier
2021-09-04 16:40 ` Drew Adams
2021-09-05 19:27 ` John Yates
2021-09-07 3:16 ` Richard Stallman
2021-09-07 15:31 ` Barry Fishman
2021-09-09 3:07 ` Richard Stallman
2021-09-09 14:07 ` André A. Gomes
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=83k0jql32w.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=andremegafone@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=john@yates-sheets.org \
--cc=monnier@iro.umontreal.ca \
--cc=rms@gnu.org \
--cc=theophilusx@gmail.com \
/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.