>Again I suggest that the best way for a new contributor
>to contribute to the JDE is to develop the contribution as
>a stand-alone module rather than as a modification to existing
>code. That gives me and other users a chance to evaluate
>and try out the changes without having to commit to including
>it in the core until JDE users are positive that it is generally
useful,
>robust, and consistent with the overall design of the JDE.
Well... perhaps I didn't explain what I'd done very well because
that's what I thought I'd done.
I've written the file as a replacement jde-compile.el but none of the
JDE functions is affected.
That means that you can still do C-V-C and get (jde-compile).
Trouble is that if you have any relative paths set then it won't
compile properly.
So what am I supposed to do? duplicate all the jde-compile options in
order to deliver a completly seperate module?
Nic
