RE: Specifying plist requirements in defcustom?

[Drew Adams]

> >> From what I could tell, this worked, but I was also to have a user-
> >> friendly customization interface when a user, say, clicked 
> >> customoize corext-enlistments.  I'd like a prompt for the symbol-name,
> >> and the individual property list values: branch, drive, and path.
> >> It seems that to acheive something like this, I'd need to just make them
> >> alists....
> > 
> > You'll have to extend Customize to get that, AFAIK. Or 
> > write your own command to customize this particular option.
> > Customize doesn't really guide you with prompts and such.
> > Customize could use a little more guidance, especially for
> > complex structures such as this one.
> 
> I do not think that you have to extend Customize. Writing a new widget
> type should be enough.

I call that extending Customize. Customize out of the box won't provide that
behavior.

~All you have to do is write...~ means that it's not there already. Playing with
widgets is, in my book, extending Customize. And it's not necessarily a
clear-cut exercise.