bug#1319: marked as done (Change in where-is-internal causing describe-key problems)

[Emacs bug Tracking System]

Your message dated Sat, 15 Nov 2008 01:22:27 -0500
with message-id <87y6zljyos.fsf@cyd.mit.edu>
and subject line Re: bug#1319: Change in where-is-internal causing describe-key 
problems
has caused the Emacs bug report #1319,
regarding Change in where-is-internal causing describe-key problems
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact don@donarmstrong.com
immediately.)


-- 
1319: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=1319
Emacs Bug Tracking System
Contact don@donarmstrong.com with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> Change in where-is-internal causing describe-key problems
>
>
>
>
> Date: 
>
> Sat, 8 Nov 2008 19:19:57 -0800
>
>
>
>
> The behaviour of where-is-internal has changed in CVS emacs. Enter
> view mode, M-: (where-is-internal 'self-insert-command nil nil nil) :
>
>   22.2  => ([491520] [458752] [442368] [425984] [409600]...)
>   CVS   => ([(128 . 4194303)])
>
> This change breaks describe-function-1, used internally in
> describe-key, causing a bound key to be printed as a non-ascii
> character in some conditions. To reproduce the problem:
>
>   emacs -Q
>   C-h k k
>   Switch to the *Help* buffer
>   C-h k k
>
> where-is-internal seems to be buggy, but perhaps describe-function-1
> should also be doing more checking. I'm not sure if it should handle
> input of the form ([(128 . 4194303)]) or not.
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#1319: Change in where-is-internal causing describe-key problems
>
>
>
>
> Date: 
>
> Sat, 15 Nov 2008 01:22:27 -0500
>
>
>
>
> I checked in a slightly simpler fix to describe-function-1.  It's
> probably not necessary to lose too much hair over this part of the code.
>
>
> --- End Message ---