> Now, however, I'm prepared to revisit this issue. I can think of way to
> make this work, for example, when updating variables, I could go through
> all the JDE variables and mark those that were customized by the current
> project. Variables customized by other open projects would be reset to
> their default values. However, before doing this, I'd be interested in
> why
> people think saving only customized variables is a good idea.
>
> I should also note that I am toying with the idea of having project
> hierarchies where subprojects could inherit or override the settings of
> parent projects or even those in the .emacs file. The way this would works
> is fairly simple, the JDE would apply all the prj.el files found in the
> current projects directory tree. Settings found lower down in the tree
> would shadow settings higher in the tree (override capability).
>
>
>
>
This project hierarchies is what I suspect most ppl want when we say
to only save customized variables. The main reason I want this is so I
don't have to define my templates more than once. So I've actually gone
through and manually edited my prj.el files to remove the jde-gen stuff so
that it reverts to the defaults from my .emacs file.
It seems that really the only way to handle this (and avoid the
problem you described) is to revert to the system defaults (i.e. the values
from your .emacs file) and then apply the prj.el file, overwriting any
defaults.
David
