GNU bug report logs -
#59886
Manual error in (elisp) Searching Keymaps regarding keymap char properties?
Previous Next
Reported by: hokomo <hokomo <at> airmail.cc>
Date: Wed, 7 Dec 2022 16:31:02 UTC
Severity: normal
Done: Eli Zaretskii <eliz <at> gnu.org>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 59886 in the body.
You can then email your comments to 59886 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#59886
; Package
emacs
.
(Wed, 07 Dec 2022 16:31:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
hokomo <hokomo <at> airmail.cc>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Wed, 07 Dec 2022 16:31:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
Hello,
The psuedo-Lisp code presented in the manual (elisp) Searching
Keymaps says:
(if (get-text-property (point) 'local-map)
(FIND-IN (get-char-property (point) 'local-map))
(FIND-IN (current-local-map)))
Why does the condition use `get-text-property', but then the
consequent uses `get-char-property'? Shouldn't they both be
`get-char-property'? According to (elisp) Active Keymaps:
"If there is a 'local-map' /text or overlay/ property at point,
that specifies the local keymap to use, in place of the buffer's
default local keymap."
Am I missing something?
Additionally, perhaps the two paragraphs in (elisp) Active Keymaps
that mention the `keymap` and the `local-map' property (search for
"property") should be reworded slightly to emphasize that the
search prefers the overlay property over the text property, since
that's how `get-char-property' is documented to work. Maybe change
the ordering of "text or overlay" to "overlay or text", along with
an explicit emphasis?
hokomo
Reply sent
to
Eli Zaretskii <eliz <at> gnu.org>
:
You have taken responsibility.
(Sat, 10 Dec 2022 13:08:01 GMT)
Full text and
rfc822 format available.
Notification sent
to
hokomo <hokomo <at> airmail.cc>
:
bug acknowledged by developer.
(Sat, 10 Dec 2022 13:08:02 GMT)
Full text and
rfc822 format available.
Message #10 received at 59886-done <at> debbugs.gnu.org (full text, mbox):
> From: hokomo <hokomo <at> airmail.cc>
> Date: Wed, 07 Dec 2022 17:21:36 +0100
>
>
> Hello,
>
> The psuedo-Lisp code presented in the manual (elisp) Searching
> Keymaps says:
>
> (if (get-text-property (point) 'local-map)
> (FIND-IN (get-char-property (point) 'local-map))
> (FIND-IN (current-local-map)))
>
> Why does the condition use `get-text-property', but then the
> consequent uses `get-char-property'? Shouldn't they both be
> `get-char-property'? According to (elisp) Active Keymaps:
>
> "If there is a 'local-map' /text or overlay/ property at point,
> that specifies the local keymap to use, in place of the buffer's
> default local keymap."
>
> Am I missing something?
>
> Additionally, perhaps the two paragraphs in (elisp) Active Keymaps
> that mention the `keymap` and the `local-map' property (search for
> "property") should be reworded slightly to emphasize that the
> search prefers the overlay property over the text property, since
> that's how `get-char-property' is documented to work. Maybe change
> the ordering of "text or overlay" to "overlay or text", along with
> an explicit emphasis?
Thanks, I've changed the example to use get-char-property.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Sun, 08 Jan 2023 12:24:08 GMT)
Full text and
rfc822 format available.
This bug report was last modified 2 years and 241 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.