GNU bug report logs - #1319
Change in where-is-internal causing describe-key problems

Previous Next

Package: emacs;

Reported by: "Geoff Gole" <geoffgole <at> gmail.com>

Date: Sun, 9 Nov 2008 03:30:03 UTC

Severity: normal

Done: Chong Yidong <cyd <at> stupidchicken.com>

Bug is archived. No further changes may be made.

Full log


Message #15 received at 1319 <at> emacsbugs.donarmstrong.com (full text, mbox):

From: martin rudalics <rudalics <at> gmx.at>
To: Geoff Gole <geoffgole <at> gmail.com>
Cc: 1319 <at> debbugs.gnu.org
Subject: Re: bug#1319: Change in where-is-internal causing describe-key problems
Date: Tue, 11 Nov 2008 13:40:39 +0100
> 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




This bug report was last modified 16 years and 246 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.