From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: 22334@debbugs.gnu.org
Subject: bug#22334: 25.1.50; Better sorting of blocks in describe-bindings
Date: Sun, 31 Oct 2021 18:47:46 -0700 [thread overview]
Message-ID: <87sfwgir3x.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <874men77k8.fsf@ericabrahamsen.net>
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> Yes, I no longer see the string [no bindings], though I do see the
>> recentf-mode header with no bindings. That doesn't really bother me. The
>> hide/show heading toggles work great, and the whole thing is much more
>> usable.
>
> Yes, I see the empty recentf-mode thing now, too (after starting
> recentf-mode). Hm... oh, the map is empty? I can't say that I
> understand why that map exists, but I think that instead of outputting
> an empty section, it should just skip it.
If the point of `describe-bindings' is to show you which (potentially
shadowing) bindings are in effect, and not which minor modes are in
effect, then yes, I agree that section could be skipped.
next prev parent reply other threads:[~2021-11-01 1:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-09 3:31 bug#22334: 25.1.50; Better sorting of blocks in describe-bindings Eric Abrahamsen
2016-01-09 7:41 ` Eli Zaretskii
[not found] ` <87mvsf57v7.fsf@ericabrahamsen.net>
2016-01-09 12:42 ` Eli Zaretskii
2016-01-09 13:05 ` Andreas Schwab
2016-01-09 16:15 ` Eli Zaretskii
2016-01-10 1:16 ` Eric Abrahamsen
2016-01-10 9:04 ` Andreas Schwab
2016-01-10 15:45 ` Eli Zaretskii
2016-01-11 1:33 ` Eric Abrahamsen
2016-02-16 7:14 ` Lars Ingebrigtsen
2021-10-31 22:28 ` Lars Ingebrigtsen
2021-11-01 1:29 ` Eric Abrahamsen
2021-11-01 1:38 ` Lars Ingebrigtsen
2021-11-01 1:47 ` Eric Abrahamsen [this message]
2021-11-01 2:30 ` Lars Ingebrigtsen
2021-11-01 2:18 ` Lars Ingebrigtsen
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=87sfwgir3x.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=22334@debbugs.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).