From: JD Smith <jdtsmith@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 68236@debbugs.gnu.org
Subject: bug#68236: [PATCH] help.el: allow help-quick to use local commands/quick-sections
Date: Thu, 4 Jan 2024 08:45:50 -0500 [thread overview]
Message-ID: <721ABC11-E691-43F9-9034-F375240C2E20@gmail.com> (raw)
In-Reply-To: <83a5ply2ca.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1042 bytes --]
> On Jan 4, 2024, at 2:39 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>
> Please describe in more detail how would people use this for their
> personal "quick help", because I don't think I understand well enough
> what you have in mind.
For example, an org user may
(add-to-list 'help-quick-sections
'("Org"
(org-ctrl-c-star . "Compute table/change heading ")
(org-ctrl-c-ret . "Table hline/insert heading")))
so that from org-buffers, C-h C-q adds a new section:
Org
C-c * Compute table/change heading
C-c RET Table hline/insert heading
Most likely users willing to customize `help-quick-sections’ would remove existing sections with commands they know well.
> In any case, such a change will need suitable changes for
> documentation.
Do you mean documentation for the `help-quick-sections' variable? How about turning this into a defcustom? This would allow more advanced users to fully customize what “quick help” they want.
[-- Attachment #2: Type: text/html, Size: 5390 bytes --]
next prev parent reply other threads:[~2024-01-04 13:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 3:08 bug#68236: [PATCH] help.el: allow help-quick to use local commands/quick-sections JD Smith
2024-01-04 7:39 ` Eli Zaretskii
2024-01-04 13:45 ` JD Smith [this message]
2024-01-04 13:57 ` Eli Zaretskii
2024-01-05 1:28 ` JD Smith
2024-01-05 8:40 ` Eli Zaretskii
2024-01-05 17:00 ` JD Smith
2024-01-10 12:51 ` Stefan Kangas
2024-01-10 13:53 ` Eli Zaretskii
2024-01-10 15:46 ` JD Smith
2024-01-10 15:50 ` Stefan Kangas
2024-01-10 15:58 ` Eli Zaretskii
2024-01-10 22:49 ` JD Smith
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=721ABC11-E691-43F9-9034-F375240C2E20@gmail.com \
--to=jdtsmith@gmail.com \
--cc=68236@debbugs.gnu.org \
--cc=eliz@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).