Re: emacs19 supported? what about emacs18?
Chris Waters <email@example.com> writes:
> We seem to have the following:
> ~ $ grep-available -Fprovides -spackage emacsen
> package: xemacs21-gnome-mule-canna-wnn
> package: xemacs21-gnome-mule
> package: xemacs21-gnome-nomule
> package: xemacs21-mule
> package: emacs20
> package: emacs21
> package: emacs20-dl
> package: xemacs21-mule-canna-wnn
> package: xemacs21-nomule
> That isn't enough flavors!?!
I miss the latest stable XEmacs version, 21.1. (xemacs21 is 21.4 which
is a gamma release and the differences to 21.1 are quite noticable if
you are programming elisp).
>> and it's easier to fully grasp what's going on when we are on older
> How so? Personally, I think that font-lock mode at the console alone
> is enough reason to justify switching to emacs21. But you're not
> forced to use any of the new features in 20/21 if you don't want to.
At the risk of starting the old flamewar: You are forced to deal with
Mule in emacs20 and emacs21. Emacs19 is binary clean, I believe Emacs
22 will be binary clean again (using Unicode internally). But I can
understand if it takes too much resources to support too many
To UNSUBSCRIBE, email to firstname.lastname@example.org
with a subject of "unsubscribe". Trouble? Contact email@example.com