unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Bob Rogers <rogers@rgrjr.com>
Cc: 62279@debbugs.gnu.org
Subject: bug#62279: Add an option to restore C-h b "Prefix Command" output
Date: Sun, 19 Mar 2023 21:35:37 +0200	[thread overview]
Message-ID: <83zg888rg6.fsf@gnu.org> (raw)
In-Reply-To: <m3bkko7dah.fsf@orion.rgrjr.com> (message from Bob Rogers on Sun,  19 Mar 2023 12:26:46 -0700)

> From: Bob Rogers <rogers@rgrjr.com>
> Date: Sun, 19 Mar 2023 12:26:46 -0700
> 
>    Pursuant to the 'No more "Prefix Command" in C-h m' discussion in the
> emacs-devel list.

Thanks.

> --- a/etc/NEWS
> +++ b/etc/NEWS
> @@ -61,6 +61,11 @@ This allows the user to customize the prompt that is appended by
>  This is used for displaying the time and date components of
>  'display-time-mode'.
>  
> +** New user option 'describe-bindings-show-prefixes'.
> +If true (the default is false), restores the "Prefix Command" entries

We use "If non-nil", not "If true".  And similarly for "false".

> +in 'describe-binding' ('C-h b') output for keys that are prefixes, the
> +details of which are shown later (regardless of this option setting).

This NEWS entry should go to where the change in "C-h b"s behavior is
described in NEWS (on emacs-29 branch), and should be reworded to tell
users how to get the previous behavior back ("To get the previous
behavior back, customize ...").

> +(defcustom describe-bindings-show-prefixes nil
> +  "Non-nil shows prefixes in the output buffer of `describe-bindings'."
> +  :type 'boolean
> +  :group 'help
> +  :version "30.1")

This should be "29.1".  Since the behavior change was introduced in
Emacs 29, we need to add this option in the same version.





  reply	other threads:[~2023-03-19 19:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-19 19:26 bug#62279: Add an option to restore C-h b "Prefix Command" output Bob Rogers
2023-03-19 19:35 ` Eli Zaretskii [this message]
2023-03-19 19:59   ` Bob Rogers
2023-03-23  8:33     ` Eli Zaretskii

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=83zg888rg6.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=62279@debbugs.gnu.org \
    --cc=rogers@rgrjr.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).