"Lennart Borgman (gmail)" <[EMAIL PROTECTED]> writes:
> There is something wrong with the initialization of
> minibuffer-prompt-properties. Custom complains that it is
>
> CHANGED outside Customize; ...
>
I don't understand why minibuffer-prompt-properties need to be
a defcustom. What properties would a user want to add???
C-code initializes it like this:
Vminibuffer_prompt_properties
= Fcons (intern ("read-only"), Fcons (Qt, Qnil));
faces.el has this to add:
(setq minibuffer-prompt-properties
(append minibuffer-prompt-properties (list 'face 'minibuffer-prompt)))
simple.el completely overrides the value (but furtunately commented out):
;(setq minibuffer-prompt-properties
; (list 'modification-hooks '(minibuffer-prompt-modification)
; 'insert-in-front-hooks '(minibuffer-prompt-insertion)))
The defcustom comes from cus-start.el:
(minibuffer-prompt-properties
minibuffer
(list
(checklist :inline t
(const :tag "Read-Only"
:doc "Prevent prompt from being modified"
:format "%t%n%h"
:inline t
(read-only t))
(const :tag "Don't Enter"
:doc "Prevent point from ever entering prompt"
:format "%t%n%h"
:inline t
(point-entered minibuffer-avoid-prompt)))
(repeat :inline t
:tag "Other Properties"
(list :inline t
:format "%v"
(symbol :tag "Property")
(sexp :tag "Value"))))
"21.1")
--
Kim F. Storm <[EMAIL PROTECTED]> http://www.cua.dk
_______________________________________________
emacs-pretest-bug mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
