From: Ihor Radchenko <yantar92@posteo.net>
To: Yuval Langer <yuval.langer@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: [POLL] Add command names to key bindings in Org Guide? (was: Suggestion: for each listed keybinding, also name the command)
Date: Fri, 05 May 2023 11:01:35 +0000 [thread overview]
Message-ID: <87y1m3m48g.fsf@localhost> (raw)
In-Reply-To: <CAK0OjG2hOJry4L4TfefkdKQp3ALX7zML_NwS=gqhD79UE7O42g@mail.gmail.com>
Yuval Langer <yuval.langer@gmail.com> writes:
> For many commands, I find it helpful to first learn their names before
> learning their keybindings. The org-mode guide does not include
> command names.
>
> I want to add command names into the org-mode guide. I have attached
> an example of such an addition.
Will it be useful?
Technically, adding the command name will increase the Org Guide size,
which is a bit against its idea of compactness.
On the other hand, new users may benefit from seeing the command names
alongside with the bindings, especially users of pre-packages Emacs
where the bindings may be shadowed by evil-mode and the likes.
WDYT?
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-05-05 10:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 10:51 Suggestion: for each listed keybinding, also name the command Yuval Langer
2023-05-05 11:01 ` Ihor Radchenko [this message]
2023-05-05 13:45 ` [POLL] Add command names to key bindings in Org Guide? Esteban Ordóñez
2023-05-05 13:59 ` Ihor Radchenko
2023-05-06 5:26 ` [POLL] Add command names to key bindings in Org Guide? (was: Suggestion: for each listed keybinding, also name the command) Adham Omran
2023-05-06 11:40 ` Corwin Brust
2023-05-06 6:25 ` Jens Neuhalfen
2023-07-19 9:53 ` Ihor Radchenko
2023-05-07 13:49 ` Suggestion: for each listed keybinding, also name the command Yuval Langer
2023-05-10 11:30 ` Ihor Radchenko
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y1m3m48g.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=yuval.langer@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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.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).