Re: [drew.adams@oracle.com: RE: Customize doc strings and tagstrings do not respect \\<...> and \\[...]]

[Andreas Schwab <schwab@suse.de>]

"Drew Adams" <drew.adams@oracle.com> writes:

> 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
>   :tag "`\\<minibuffer-local-map>\\[next-history-element]'.")
>
> and this:
>
> (defcustom titi 'tata "OK" :type
>  '(choice
>    (const :tag "`\\<minibuffer-local-map>\\[next-history-element]'."
>           tata)))
>
> I see in Customize what I reported initially:
> \<minibuffer-local-map>\[next-history-element] (one level of \ removed).

Why do you think this is a bug?  The tag contains exactly this text.

> 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.

No.  This is the correct rendition of \<my-map> when my-map is not
defined.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."