From: martin rudalics <rudalics@gmx.at>
To: Geoff Gole <geoffgole@gmail.com>
Cc: 1319@emacsbugs.donarmstrong.com
Subject: bug#1319: Change in where-is-internal causing describe-key problems
Date: Tue, 11 Nov 2008 13:40:39 +0100 [thread overview]
Message-ID: <49197D47.4080406@gmx.at> (raw)
In-Reply-To: <f5bc73230811110314i86b57f3la079f8c1d17f8513@mail.gmail.com>
> I saw that, but I thought it was more likely to be a cheap early
> out than a test that was ever meant to be bulletproof.
Maybe you were right in thinking so, I don't know.
> This code later in the describe-function-1 should handle the case
> where that test fails but there are many keys bound to
> self-insert-command:
>
> (when keys
> (princ (if remapped ", which is bound to " "It is bound to "))
> ;; If lots of ordinary text characters run this command,
> ;; don't mention them one by one.
> (if (< (length non-modified-keys) 10)
> (princ (mapconcat 'key-description keys ", "))
> (dolist (key non-modified-keys)
> (setq keys (delq key keys)))
> (if keys
> (progn
> (princ (mapconcat 'key-description keys ", "))
> (princ ", and many ordinary text characters"))
> (princ "many ordinary text characters"))))
>
> And indeed in 22.2, it does. But the aforementioned change in
> where-is-internal breaks it.
What precisely was the change in `where-is-internal' that broke it?
martin
next prev parent reply other threads:[~2008-11-11 12:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87y6zljyos.fsf@cyd.mit.edu>
2008-11-09 3:19 ` bug#1319: Change in where-is-internal causing describe-key problems Geoff Gole
2008-11-11 9:50 ` martin rudalics
[not found] ` <f5bc73230811110314i86b57f3la079f8c1d17f8513@mail.gmail.com>
2008-11-11 12:40 ` martin rudalics [this message]
2008-11-11 14:12 ` Geoff Gole
2008-11-11 19:05 ` martin rudalics
2008-11-12 3:01 ` Stefan Monnier
2008-11-12 18:32 ` martin rudalics
2008-11-15 6:30 ` bug#1319: marked as done (Change in where-is-internal causing describe-key problems) Emacs bug Tracking System
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=49197D47.4080406@gmx.at \
--to=rudalics@gmx.at \
--cc=1319@emacsbugs.donarmstrong.com \
--cc=geoffgole@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 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.