> * In message <[EMAIL PROTECTED]>
> * On the subject of "Re: ANN: JDE-2.2.5 available"
> * Sent on Sat, 14 Oct 2000 01:28:51 +0000
> * Honorable Paul Kinnucan <[EMAIL PROTECTED]> writes:
>
> The traditional way of customizing Emacs is to use setq forms to set
> the values of customization variables in the Emacs initialization
> (.emacs ) file. This method does not work for JDE customization
> variables. To set a JDE customization variable, you must use the
> customization buffer for a variable (see the Emacs online manual for
> information on the customization feature).
This is very unfortunate.
Many old-time Emacs users never use `customize' - we consider it a
wasteful bloat-ware. Most Emacs packages which use `customize' let us
not to use `customize'. It would be nice if you could accommodate the
old-timers too...
Fortunately, JDE comes with the source code, so I could figure out that
creating an empty jde-project-file-name in the current directory would
fix my problem.
An alternative is to set the variables with `setq-default' and also
`put' their `saved-value'.
I have some more questions:
1. why do you use `eval' in `jde-set-variables-init-value'? This seems
to be unnecessary: you are evaluating strings.
2. in `jde-find-project-file', you use (find ... (directory-files))
while `file-exists-p' seems to foot the bill just fine.
3. you use `mapcar' in `jde-set-variables-init-value', and you don't
need the list it conses. why not use `dolist' or `mapc'?
Thanks for your kind reply!
--
Sam Steingold (http://www.podval.org/~sds)
Support Israel's right to defend herself! <http://www.i-charity.com/go/israel>
Lisp: its not just for geniuses anymore.
