unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: JD Smith <jdtsmith@gmail.com>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
	68236@debbugs.gnu.org, Philip Kaludercic <philipk@posteo.net>
Subject: bug#68236: [PATCH] help.el: allow help-quick to use local commands/quick-sections
Date: Wed, 10 Jan 2024 10:46:22 -0500	[thread overview]
Message-ID: <FFDE0EB0-66B8-48EA-97AE-02E512CEAACE@gmail.com> (raw)
In-Reply-To: <CADwFkm=D0FdxoiUi3Q5VfT2rz8uD-TrvXDf_7y5cKG9UYOc54w@mail.gmail.com>




> On Jan 10, 2024, at 7:51 AM, Stefan Kangas <stefankangas@gmail.com> wrote:
> 
> We could also add a separate command to show only those commands somehow
> in a similar way to `help-quick-toggle'.

One advantage of this approach is you can craft your *own* short command description, if the docstring or command name is not clear to you (things like org-ctrl-return being prime examples).  But what about instead of a separate command to remember, just creating an (optional) section in the existing help-quick popup, for local commands?  where-is-internal would consult the global keymap for the global commands, and the current buffer’s keymap for the locals. 




  parent reply	other threads:[~2024-01-10 15:46 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
2024-01-10 15:46             ` JD Smith [this message]
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=FFDE0EB0-66B8-48EA-97AE-02E512CEAACE@gmail.com \
    --to=jdtsmith@gmail.com \
    --cc=68236@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --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).