From: Eli Zaretskii <eliz@gnu.org>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: 22334@debbugs.gnu.org
Subject: bug#22334: 25.1.50; Better sorting of blocks in describe-bindings
Date: Sat, 09 Jan 2016 09:41:29 +0200 [thread overview]
Message-ID: <83lh7znqs6.fsf@gnu.org> (raw)
In-Reply-To: <874men77k8.fsf@ericabrahamsen.net> (message from Eric Abrahamsen on Sat, 09 Jan 2016 11:31:03 +0800)
> From: Eric Abrahamsen <eric@ericabrahamsen.net>
> Date: Sat, 09 Jan 2016 11:31:03 +0800
>
> When using `describe-bindings' to see the current key bindings in
> effect, I'd like the major mode bindings to be sorted to the top of the
> buffer, followed by the minor modes.
That's what I see we do now: the major mode is first, followed by the
minor modes. There's a part with links to minor modes, in case the
user knows which minor mode she wants to read about.
> Right now the sorting of blocks seems random, though every time the
> top block is twenty screens or so of self-inserting bindings (or
> maybe it's compose sequences?) which are never what I want to see,
> and are a pain to scroll past.
Please show an example of that, because this is definitely specific to
the major mode. E.g., I don't see this for *scratch*.
> While we're at it, minor modes with no bindings in effect could just
> as well be omitted.
It only takes a line or two; omitting that would be losing
information, IMO.
next prev parent reply other threads:[~2016-01-09 7:41 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 [this message]
[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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83lh7znqs6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=22334@debbugs.gnu.org \
--cc=eric@ericabrahamsen.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.