Re: Try loading ~/.eclipse/custom.lisp before ~/.eclipse

Christian Lynbech <[email protected]> writes:

> How about making the default config file name be a configuration
> option and perhaps adding a switch to the `eclipse' script that allows
> a per-session specification to be made?

Also, since the configuration is loaded before we load the initial
theme, how about letting the user specify the initial theme in the
~/.eclipse too?  I'm unsure about the best approach, but perhaps we
could do:

	(setf (decoration-theme) *inital-theme*))
      (init-edges-cursors)
      (initialize-clone))))

instead of:

	(setf (decoration-theme) "microGUI"))
      (init-edges-cursors)
      (initialize-clone))))

And then, in globals.lisp, we'd say:

    (defparameter *initial-theme* "microGUI")

Thus, if the user wants brushed-metal as his default theme, he could put
the following in his ~/.eclipse:

    (defparameter *initial-theme* "brushed-metal")

Erik.

_______________________________________________
http://lists.unlambda.com/mailman/listinfo/eclipse