From: "Esteban Ordóñez" <quiliro@riseup.net>
To: emacs-orgmode@gnu.org
Subject: Re: [POLL] Add command names to key bindings in Org Guide?
Date: Fri, 05 May 2023 13:45:28 +0000 [thread overview]
Message-ID: <54acdb9e225508581a94b1865f4515c6@riseup.net> (raw)
In-Reply-To: <87y1m3m48g.fsf@localhost>
El 2023-05-05 06:01, Ihor Radchenko escribió:
> 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?
I think that mentioning command names would help a lot to understand the
objective of the command and would also help to find its documentation.
A common problem for me was [is?] that I could not find the place where
there is more information about something. The size of the document is
not as important, if it is easy to find your way in it.
next prev parent reply other threads:[~2023-05-05 13:46 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 ` [POLL] Add command names to key bindings in Org Guide? (was: Suggestion: for each listed keybinding, also name the command) Ihor Radchenko
2023-05-05 13:45 ` Esteban Ordóñez [this message]
2023-05-05 13:59 ` [POLL] Add command names to key bindings in Org Guide? 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=54acdb9e225508581a94b1865f4515c6@riseup.net \
--to=quiliro@riseup.net \
--cc=emacs-orgmode@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/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).