Per Abrahamsen <abraham(a)dina.kvl.dk> writes:
I'm looking into porting the theme support from XEmacs into
Emacs.
Sorry for not responding earlier. The reason is that I have some
aborted work on the UI part that I cannot seem to find :-(. The rest
of my work (i.e. the basic infrastructure) is in the XEmacs
CVS/betas.
I have to finish my thesis before I can do any more serious work on it.
However, looking at the 21.0 source there are also some features
that
could be ported the other way, like:
Doc improvements.
Always useful.
Using customize to set local variables
If this is the same as in 20.4 then I consider this extremely ugly.
New keyword :set-after (explicit dependencies between
options)
new font attributes
Some of the later could perhaps be emulated with wmperry's font.el
package (same way the current font attributes are handled).
Note that in XEmacs 21.2 I've been trying to move away from font.el
(and use frob-face-property functions), however that also got stuck by
time constraints.
If I start working on these, will someone look at it?
Yes. Don't expect it to be before the end of January for the serious
stuff. :-(
Another thing:
I and Dave Love had sort-of agreed that any new options in the
customize-set-variables lines would be using keywords (starting with
the comment stuff). Presumably that would greatly enhance cross Emacs
and cross version compatibility. If you do that on the FSF side I'll
do it here.
Jan
P.S. Would it be possible (politically) to insert a comment in the
custom.el files to _please_ always contact us on customize options
changes. Currently customize options are portable across Emacsen. I
would love for it to stay that way.