On 03/ 1/11 08:02 PM, Stephen J. Turnbull wrote:
And when the XEmacs 21.5 code base goes stable? What then? Is that
really as good as
(if (not (emacs-version>= 21 5)) (require 'ess-site))
which right now has the same effect, but will have a different effect
when this code base becomes stable?
We'll all rejoice then, will we not? :o)
I also don't understand why 21.5 doesn't need ess-site, but
very fishy to me. If there's 21.4-specific code in ESS, I don't think
it belongs in a site config file, but rather in an appropriately named
That is, although I see how it could be used to temporarily work
around the real issue (which is hidden in ess-site somewhere), it
seems to me you're storing up trouble for the future.
Well no, the issue was
that the "feature" was in xemacs-beta,
not ESS. Like you say, this would have been only temporary while I
came up with a work-around for the package/lisp directory "feature".
But, as you say, there is another way which I am using now:
(if xemacs-betaname nil (require 'ess-site))
Rodney Sparapani Center for Patient Care and Outcomes Research
Sr. Biostatistician http://www.mcw.edu/pcor
4 wheels good, 2 wheels better! Medical College of Wisconsin (MCW)
WWLD?: What Would Lombardi Do? Milwaukee, WI, USA
XEmacs-Beta mailing list