Re: [lennart.borgman@gmail.com: C-h k does not catch text properies keymaps]

["Lennart Borgman (gmail)" <lennart.borgman@gmail.com>]

David Kastrup wrote:
> Chong Yidong <cyd@stupidchicken.com> writes:
> 
>> Richard Stallman <rms@gnu.org> writes:
>>
>>> Would someone please debug this and ack?
>> Didn't David Kastrup rewrite the key-binding code a few months ago, to
>> handle this case?
> 
> The "problem" is more with `describe-key'.  However:
> 
>>> (defun temp-test-mouse-ctrl-h-k()
>>>   (interactive)
>>>   (switch-to-buffer-other-window (get-buffer-create "test mouse buffer"))
>>>   (goto-char (point-max))
>>>   (let ((map (make-sparse-keymap))
>>>         (txt "click here"))
>>>     (define-key map [mouse-1] '(lambda()
>>>                                  "This is the lambda for mouse-1"
>>>                                  (interactive)
>>>                                  (message "lambda for mouse-1 here")))
>>>     (define-key map [f2] '(lambda()
>>>                             "This is the lambda for f2"
>>>                             (interactive)
>>>                             (message "lambda for f2 here")))
>>>     (put-text-property 0 (length txt) 'face '(:underline t :foreground
>>> "red") txt)
>>>     (put-text-property 0 (length txt) 'mouse-face 'highlight txt)
>>>     (put-text-property 0 (length txt) 'keymap map txt)
>>>     (insert "\n" txt)
>>>     ))
>>>
>>> Do
>>>
>>>    M-x temp-test-mouse-ctrl-h-k
>>>    C-h k
>>>
>>> and then click the red underlined text with mouse button 1. It will say
>>>
>>>   <down-mouse-1> at that spot runs the command mouse-drag-region
>>>
>>> which is not correct.
> 
> Actually, it _is_ correct.  Do
> 
> M-x debug-on-entry RET mouse-drag-region RET
> 
> and you'll find that clicking at that spot indeed first runs
> mouse-drag-region.


Ok, thanks. I can see it is partly correct and useful. But the 
information about the other function, should not that be shown too?