>>>> "SJT" == Stephen J Turnbull
<turnbull(a)sk.tsukuba.ac.jp>:
SJT> Custom doesn't know about package dependencies, if that's what you
SJT> mean. So uniquify )or any other package) won't get used at all unless
SJT> it is require'd or autoloaded somewhere. Custom doesn't do that for
SJT> you at this point.
maybe this is something I'm confused about - I had thought that customizing
something in a pkg would cause that pkg to be required in subsequent
sessions
SJT> If you mean uniquify _is_ getting used but that customization is being
SJT> forgotten unless you do the require _first_, then Custom may be buggy
SJT> (uniquify.el seems to be properly Custom-ized).
*that's* it...
SJT> Check that uniquify is getting used by doing a (featurep 'uniquify)
it's not
SJT> (I think the post <##>
SJT> style is the default whether or not uniquify is loaded, so you
SJT> wouldn't be able to tell by looking at buffer names).
right
>>>> "JV" == Jan Vroonhof
<vroonhof(a)math.ethz.ch>:
JV> I guess uniquify needs a :require in the defcustom of its main
JV> enabling variable.
I'm not sure what the main enabling variable is - I tried adding :require
to the defcustom for uniquify-buffer-name-style, but that didn't do it -
I may not have done it correctly, though, since obviously I don't
understand custom very well...
-JT