Ben Speakmon <[EMAIL PROTECTED]> writes:
> The way we've been doing this is to take a clean .emacs file, load the
> JDE, and use the JDE customizer to set the constant properties. We then
> "save for future sessions" the variables, which writes them to the
> .emacs. We pass that around whenever there is a change to our build
> environment or whatever.
Sadly, this looks like the way to go.
> I think something was said earlier about the JDE variables being
> *required* to be set through customize first. Anybody else know more?
This seems to be true. As feature request I suggest an order like
first prj.el, custom-set-variables in .emacs, setq statements, and
last the JDE defaults.
Thanks
Gerd
