[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: address@hidden: RE: Customize doc strings and tagstrings do not resp
RE: address@hidden: RE: Customize doc strings and tagstrings do not respect \\<...> and \\[...]]
Sat, 4 Mar 2006 09:55:53 -0800
> (defcustom foo nil
> "*Behavior of `\\<my-map>\\[my-cmd]' when ...."
> :type 'boolean)
> when you get to the Customize buffer you see this:
> Behavior of `\<my-map>\[my-cmd]' when....
> Note that one level of backslash is removed.
I can't reproduce this. For example,
M-x customize-option RET Info-enable-edit
displays the "\\<Info-mode-map>\\[Info-edit]" tag fine.
1. I believe I must have been mistaken about the doc string. But the problem
definitely exists for :tag. Try this:
(defcustom bar nil "OK" :type 'boolean
(defcustom titi 'tata "OK" :type
(const :tag "`\\<minibuffer-local-map>\\[next-history-element]'."
I see in Customize what I reported initially:
\<minibuffer-local-map>\[next-history-element] (one level of \ removed).
2. BTW, if I eval the defcustom I sent originally (quoted above), without
defining `my-map', then I get this in Customize, with a warning message
spliced into the middle of the key description:
Behavior of ` Hide Rest
Uses keymap "my-map", which is not currently defined.
M-x my-cmd' when foobaz is in the wind.
Parent groups: Nil
This appears to be another bug.