Paul Kinnucan <[EMAIL PROTECTED]> writes:
> (jde-set-project-name "projectname")
> (jde-set-variables ) ;; <-- Inserted to ensure that Save Project saves here.
> (load "jde-project-defaults") ;; This must always be last.
[...]
> CAVEAT: I have not tried the above. If you decide to try it, I'd be
> interested to
> here how it works out.
>
> If this works, I could wire something similar into the JDE, that is,
> add the capability to always load a defaults file after whatever is
> in the .emacs file or prj.el file.
Thanks for the suggestions. That gave me confidence to try the
following and having more than one customize-set-variable the system.
I have this in the .emacs file:
,----
| ;;; Use a custom file for saving options.
| (setq custom-file "~/.emacs-custom")
|
| ;;; Load custom settings from different sources.
| (load "/.../default-custom.el")
| (load custom-file)
| (load "/.../fix-custom.el")
`----
What happens: First, some default values are loaded from
`default-custom.el' (e.g. project wide classpath, which at least is a
template to show what is needed). Those values are overwritten by the
values from the custom-file, which are changed by the user thru the
customize system. The file `fix-custom.el' finally holds some values
which can not changed permanently by the user.
This setup seems to work well and my fear against multiple
customize-set-variable seems somewhat unnecessary (note: I setq
custom-file to the correct file, I never tried it without and I use
XEmacs 21.1.7).
Thanks to everybody who helped.
Gerd
