>>>>> "Paul" == Paul Kinnucan <[EMAIL PROTECTED]> writes:
>> I've had a go at implementing the first solution. The second one >> is a little more wide ranging and I think would have unexpected >> consequences. For instance using buffer-local variables would >> mean that you could not disable context switching, which I think >> you do temporarily during debugging. >> >> I've attached a "jde-custom.el" file which implements the >> defjdecustom method. It seems to be working for me at the moment. Paul> Hi Phil, Paul> I'd like to suggest another approach to this problem. I've Paul> implemented it in my sandbox and it seems to work fine. I'd Paul> like to get feedback from you and others on it. Paul> The proposed approach is the following. Paul> I have created a new command called jde-customize-option. This Paul> command displays a standard customization buffer with two Paul> additional features: Paul> (1) The "Set" menu has a new "Save to Project" Paul> option. Selecting this Paul> option sets the option to its customized value, saves the Paul> value in the current project file, and adds the variable to Paul> the JDEE's dirty variable list. (2) The existing "Erase Paul> Customization" option now erases the customization and then Paul> deletes the variable from the current project file. This Paul> solution not only eliminates the need for a defjdeoption macro Paul> it also eliminates the need to execute an additional command Paul> to save or delete the variable from the project Paul> file. Accordingly, I propose changing the jde-save-project Paul> option from a command to a function. Paul> How does this strike you? Paul I think that this is probably a neater solution than the defjdecustom solution as I said the other day. I thought it would be more work but you seem to have done it quickly enough, so I would definitely go for it. On the second topic, that is removing jde-save-project as a command, I would disagree. I partially generate my project file using an ant task that I have written, and so I use jde-save-project to create a skeleton. Having said this, I do so rarely so removing it's menu and keybinding would be fine. Of course push comes to shove I can always use `eval-expression'. I'm quite surprised here. My original patch was just to speed up project file switching rather than anything else. Things seem to have moved further in a short space of time! Cheers Phil
