[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, 04 Mar 2006 22:36:17 +0100
Gnus/5.110003 (No Gnus v0.3) Emacs/22.0.50 (gnu/linux)
"Drew Adams" <address@hidden> 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
> (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).
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
Andreas Schwab, SuSE Labs, address@hidden
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."