>>>>> "Paul" == Paul Kinnucan <[EMAIL PROTECTED]> writes:
Paul> Hi Karen,
Paul> Did you use customize to set your JDE variables in your
Paul> .emacs?
Paul> When customize first became available, I spent a lot of time
Paul> and effort to convert JDE to use this new facility because it
Paul> protects users, even experience users, from problems like the
Paul> one you just encountered. I use customize myself
Paul> religiously. I NEVER customize the JDE directly in my .emacs
Paul> file. I urge all JDE users to do so also. You'll save yourself
Paul> a lot of grief.
What Paul says is correct...up to a point!
Whilst custom is very very useful it is limited compared to
what you can do lisp by hand, although as he says it stops you making
a lot of mistakes.
If you want to do something which you can not do with custom
the best way is to call custom-set-variables (so that custom shows the
correct results), but you have to call it AFTER the auto-coded custom
set call. I do this as follows....
My .emacs these days I leave entirely to custom, and it looks like
this (with most of the custom spam cut out for brevity here. What used
it be my .emacs is now called main.el.
=====begin .emacs
;;Load my main emacs file
(setq load-path
(cons "~/emacs" load-path))
(load "main.el" )
(custom-set-variables
'(jde-run-option-properties (quote (("photofit.dir" . "f:\\photofit"))))
'(jde-cflow-switch-statement-template (quote ("blah ")))
'(jde-compile-option-command-line-args "+E")
'(browse-url-browser-function (quote browse-url-generic))
=======etc etc etc
)
;;Load the post-custom file which has code which needs to be loaded er...
;;after the custom set vars. On the whole it is used to reset custom vars
;;for specific circumstances
(load "post-custom.el")
=====end .emacs
In postcustom I have currently....
(if (equal (system-name) "LAPHROAIG")
(custom-set-variables
'(jde-run-option-properties (quote (("photofit.dir" . "e:\\photofit"))))
'(jde-db-source-directories (quote ("e:/src" "d:/home/java/sources")))
'(jde-help-docsets (quote (("javadoc" "e:\\docs\\api" nil))))))
(if (equal (system-name) "TOMATIN")
(custom-set-variables
'(jde-db-source-directories (quote ("f:/zips/src" "d:/home/java/sources")))
'(jde-help-docsets (quote (("javadoc" "f:/zips/docs/api" nil) ("javadoc"
"d:/localdoc" nil))))
'(jde-run-option-properties (quote (("photofit.dir" . "f:\\photofit"))))))
which works out which machine I am on (at home or at work) and
alters some variables appropriately. The point is that I can use
identical emacs ini files at home and at work, but with a few bits and
pieces in different places, relating to the different configurations
of my system.
Thats the way that I do it anyway.
As Paul mentioned its easy to get yourself into a mess with
editing custom stuff my hand, so I usually copy and paste the relevant
lines from the custom set variables written by emacs....
Phil
