>
> Use customize. Customize generates code in your .emacs file.
Yes - I know, but I do not want it to be part of my .emacs file.
The scenario is as follows:
Presume I write a jde-XYZ.el with stuff for integrating XYZ with jde.
In this jde-XYZ.el I provide a set of templates that should just be appended
to the already existing templates provide by jde-gen.el
Thus in a users .emacs he should write:
(require 'jde) ;; default jde
(require 'jde-XYZ) ;; load the other mode which provides some extra
templates.
How should jde-XYZ.el go about registering the new extra templates ?
> the code is created. But what a difference customization makes. By
> automating the process, it eliminates many of the coding errors that used
> to plague JDE users.
I love the customization features of emacs and it's modes - I just want a
function that semantically does the same as what the user can do through the
customization buffer (note: this is actually not a feature missing in JDE,
its a custom.el "feature"-request/search.)
> Here is the way I intended this to work:
>
> 1. You develop your own templates and store them in your .emacs file
> or in a separate file required by your .emacs file.
>
> Note that you don't have to use defcustom to create
> your templates as I have done. I used defcustom so that
> users can modify the templates in jde-gen.el without
> having to modify jde-gen.el itself.
I want to use defcustom as jde-XYZ.el also should be customizable.
> 2. Register your templates with the JDE. You do this by
> customizing jde-gen-buffer-templates to add the names of your
> templates with associated descriptive text.
Yep - but to use jde-XYZ.el it should not be required by the user to
manually register the templates provide by jde-XYZ.el...
> All of this is described in excruciating detail in the JDE User's Guide,
> but of course the user's guide the last place consulted by users looking
> for information about the JDE.
I know - I have read the user guide several times and I do not (knock on
wood) post a question here without reading/searching in the guide (or the
maillinglist archive for that matter)
Regards
Max
