>>>> "dv" == Didier Verna
<verna(a)inf.enst.fr> writes:
dv> sperber(a)informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor]) writes:
> I still don't understand. What's the meaning of "to
require another
> package (not only one feature of this package)" operationally?
dv> Well, my idea was to require at once all the features a package can
dv> provide, in the case several of them would need to be require'd
dv> explicitely.
I'm sure packages for which this makes sense already have a
"super-feature" ('w3 probably is one) which, when require'd, requires
the other ones or signs them up for autoload. I don't think it makes
sense to do special API provision for this case. However, it would
make plenty of sense to establish naming conventions for them. The
mental step from "vc" to (require 'vc-hooks) is a big one.
--
Cheers =8-} Chipsy
Friede, Völkerverständigung und überhaupt blabla