Re: [SOLVED]
>>>> Uwe Brauer <oub(a)mat.ucm.es> writes:
I don't know what is best, to modify the code for xemacs, or to
ask
the author to wrap a (if (featurep 'xemacs) around the relevant
parts of the code.
Hard to tell what is the best solution.
Telling upstream that this usage breaks XEmacs is always a good
idea. (And I think you already did that right?) What upstream then
will do about it is another deal.
Like many other packages calendar could probably benefit from being
upgraded in the XEmacs Packages Tree. In that case, when the upstream
version is not compatible with XEmacs, I would suggest just fixing it
by using the XEmacs version of functions there.
Having said that I also think we should add the optional parameter
"when" to 21.5 in order to be compatible with GNU. So this problem
will grow away. A first implementation could just accept it and
ignore it. If not useless information it seems at least not that
critical, but I'm probably ignorant.
Yours
--
%% Mats
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta