Paul Kinnucan <[EMAIL PROTECTED]> writes:
> * Implements hierarchical project files.
>
> The JDE now saves only variables that have been customized for the
> current session in project files. The JDE now loads project files in
> the following manner. It first sets all the JDE variables to their
> Emacs startup values (i.e., the default value or the value saved in
> your .emacs file). It then loads all the project files in the
> directory tree containing the current source buffer, starting with
> the topmost file.
>
> What this means is that you can now use project files to
> extend and/or override the settings in your .emacs file and
> in other project files. For example, your .emacs file can
> specify settings that are common to all your projects.
> You can put settings common to a group of projects at the
> top of the directory tree containing the projects, settings
> common to each project at the top of the directory containing
> each projects, and so on.
>
> Thanks to Nick Sieger for contributing to this enhancement.
>
I tried to use this new feature by setting the defaults values in my
emacs customization file, creating a java class in a directory not
containing any prj.el file, nor in the parent directories. Then I
changed the jde-global-classpath, saved the project (apropos project:
is there any difference anymore between "save" and "save in"?). The
resulting prj.el file contained the following line:
(jde-set-variables )
without any customizations. has somebody else tried out this new
feature and had the same result?
--
knut
