My typical usage of the JDE is to have a custom-set-variables block in
my .emacs that sets a bunch of defaults for the JDE, and then only
override a couple of the jde variables in each of my projects
(typically jde-global-classpath and a few others). I always wondered
why it was necessary to save
Thursday, March 29, 2001 11:14 AM
> To: [EMAIL PROTECTED]
> Subject: PROPOSAL: Only save customized vars in project file
>
>
> My typical usage of the JDE is to have a custom-set-variables block in
> my .emacs that sets a bunch of defaults for the JDE, and then only
> o
At 01:13 PM 3/29/01 -0600, you wrote:
>My typical usage of the JDE is to have a custom-set-variables block in
>my .emacs that sets a bunch of defaults for the JDE, and then only
>override a couple of the jde variables in each of my projects
>(typically jde-global-classpath and a few others). I al
hat. Does this fix that problem, or am I misunderstanding the issue?
/Nick
-Original Message-
From: Paul Kinnucan [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 29, 2001 1:51 PM
To: Nick Sieger
Cc: [EMAIL PROTECTED]
Subject: Re: PROPOSAL: Only save customized vars in project file
At 01:
At 01:59 PM 3/29/01 -0600, Nick Sieger wrote:
>I think I see your point about settings from projects carrying across
>project boundaries at buffer switches, but that's what the change to
>jde-load-project-file is intended to guard against - it always does a
>`jde-set-variables-init-value' and then
