At 08:13 PM 9/17/00 +0200, you wrote:
>Hi paul,
>
>thank you very much, now it works fine!
>
>But another question:
>All jde-variables are only setable via customize, means if i�m the emacs-
>administrator and if i want to pre-configure JDE in some options i must
>do this with custom-set-variables in the site-start.el or any other site-
>loaded file. It would be more convenient if the normal setq mechanism would
^^^^^^
The setq form is no longer the "normal" way to set Emacs customization
variables. The "normal" way is to use customization.
>work too. Why are you so restrictive concerning the method of
customization of JDE??
>
1) To facilitate correct configuration of the JDE.
Before customization, the most frequent problems with the JDE were caused
by people setting JDE variables incorrectly, e.g., setting a variable to a
string where a list of strings was required. The people most prone to this
kind of problem are experienced Emacs users who assume they know what the
type of a variable is and never bother to check the doc. The introduction
of customization buffers has eliminated this problem except for the
occasional diehard who insists on setq'ing the variables.
2) To permit multiple projects to be open at the same time.
Before customization, all JDE variables were buffer local to permit
multiple projects to be open simultaneously. When customization was
introduced, it did not support customization of the buffer local version of
a variable and hence the ability to customize variables differently for
different projects. The JDE addresses this problem by making most JDE
variables global and then resetting them to project-specific values
whenever a user switches from a buffer belonging to one project to a buffer
belonging to other. The project-switching mechanism gets the correct values
by loading the corresponding project file or the customized values or
default values specified by the .emacs file. The JDE gets the default or
customized values from the corresponding properties of the customization
variable. Customizing a variable sets these properties. The setq form does
not. Thus, if you use setq to customize the variables, the project
switching mechanism does not work correctlyl
- Paul
