> I see things like this fairly commonly, at the top level of the standard
> Emacs libraries:
All these examples don't seem relevant since nowhere is it suggested to the
user to load the library in her .emacs.
> To me, it makes sense to generally avoid using user options at the top level
> of the library that defines them, but I'm not sure such avoidance is always
> feasible. In any case, as the above examples show, the standard libraries
> are themselves full of counter examples.
What makes more sense is to discourage loading of packages in .emacs.
Instead users should only set vars, setup autoloads, ...
> No doubt I'm still missing something - please help me understand. I want to
> fix the "bug in the elisp library" in question, but I don't know how to
> proceed. I want a user to be able to just load the library and go
Why would she need to load the library?
Stefan
_______________________________________________
Help-gnu-emacs mailing list
Help-gnu-emacs@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gnu-emacs
