>>>>> "Paul" == Paul Kinnucan <[EMAIL PROTECTED]> writes:
>> >> This will also make it easy for third parties to piggy back into >> the JDE project system I think, without having to use the "jde-" >> namespace which the system currently depends on. >> >> I'd be quite happy to give this a go if you'd like. Might take a >> day or two (it's pub night tonight!). >> Paul> Okay. Your assignment, should you choose to accept it, is to Paul> create a macro named defjdeoption. It should do everything Paul> that defcustom does plus store a customized variable on the Paul> dirty variables list and offer the user the option to save a Paul> customization to the current project file. I shall give this a go when I get home tonight. Incidentally I think that there might be a better, if longer term solution. When you start customise from a JDE buffer the customise buffer knows which project you are talking about because it shares the same default-directory as the JDE buffer. So it should be possible to override defcustom to set its variable in a buffer-local variable, and then set all the other buffers in the same project to be the same thing. After all the only reason that project file switch has to happen at all is because defcustom doesn't do buffer-local variables. You could then relegate project files to do what they do best which is serialise the options out so that they get set between sessions (or for newly visited files in an existing project). Still if the project file switching happens quickly enough this is probably just not an issue, so it may be more effort than it's worth... Cheers Phil
