>>> Paul Kinnucan <[EMAIL PROTECTED]> seems to think that:
[ ... ]
>The only solution to this problem that I can see is to provide a
>custom-set function for JDEE variables that updates the dirty variable
>list whenever the user customizes a variable during a session. Since
>the custom-set function is also invoked by the defcustom macro to set
>the variable s default value, the JDEE's custom-set function would
>have to detect that it is being invoked by a defcustom macro and not
>update the dirty variable list. This change will require adding the
>set function to every defcustom form in the JDEE code base but is
>probably worth it.
[ ... ]
Hi Paul,
You may want to create a macro "defjdeoption" other other specific
name for any variable that is part of a project, and reserve defcustom
for variables that do not get saved. After the initial change to all
sources, this will save you lots of time in the future.
Eric
--
Eric Ludlam: [EMAIL PROTECTED], [EMAIL PROTECTED]
Home: http://www.ludlam.net Siege: www.siege-engine.com
Emacs: http://cedet.sourceforge.net GNU: www.gnu.org
