Pascal Costanza wrote:
One could use a global variable that stores one's own configuration option, for example as a plist or alist. This would have to be in the common-lisp-user package, and theoretically clashes with other such variables.
Yes. One thing I do for this is to use CL-USER variables that are named after the package involved, so as to avoid name clashes. For example, Clon uses a variable named cl-user:*com.dvlsoft.clon.dump*.
I don't think this will ever clash with anyone ;-)