From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: philipk@posteo.net, 68236@debbugs.gnu.org, jdtsmith@gmail.com
Subject: bug#68236: [PATCH] help.el: allow help-quick to use local commands/quick-sections
Date: Wed, 10 Jan 2024 15:53:26 +0200 [thread overview]
Message-ID: <83zfxdmh0p.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkm=D0FdxoiUi3Q5VfT2rz8uD-TrvXDf_7y5cKG9UYOc54w@mail.gmail.com> (message from Stefan Kangas on Wed, 10 Jan 2024 04:51:48 -0800)
> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Wed, 10 Jan 2024 04:51:48 -0800
> Cc: 68236@debbugs.gnu.org, Philip Kaludercic <philipk@posteo.net>
>
> I think a more specific cheat sheet for major modes would be more
> suitable, yes.
>
> Here's an idea that I've had:
>
> Typically, I only want to remember a few commands in each major mode.
> It would be useful to be able to mark them for highlighting or somesuch
> in the general describe-mode *Help* buffer (preferably using keys, and
> not using M-x customize, though they could persist by saving the result
> to the custom file). Then, the next time I display `describe-mode',
> they would be highlighted, in this or future sessions. How about
> something like that?
>
> We could also add a separate command to show only those commands somehow
> in a similar way to `help-quick-toggle'.
Something along these lines, yes.
next prev parent reply other threads:[~2024-01-10 13:53 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
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 [this message]
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=83zfxdmh0p.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=68236@debbugs.gnu.org \
--cc=jdtsmith@gmail.com \
--cc=philipk@posteo.net \
--cc=stefankangas@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.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).