SL Baur <steve(a)xemacs.org> writes:
1. If a symbol in XEmacs has been renamed, but the old name exists
and
is in active usage in FSF Emacs, it is (make-compatible)'d where it
was previously (make-obsolete)'ed. These are mostly done, but some
symbols have fallen through the cracks, like `eval-current-buffer'.
I do not want package authors turning off bytecompiler warnings due
to obsolescence warnings from the bytecompiler due to portability
with FSF Emacs. I consider this an XEmacs bug to be fixed.
Sometimes, not always. `window-system' is an example of otherwise.
This variables is obsolete in XEmacs. Period.
I am serious about XEmacs 21 signaling "The bloat stops
here."
XEmacs shall not be the prime example of a huge, bloated pig of a
piece of software. Deleting stuff no one has used, and the editor
has signalled for years as being on the verge of imminent deletion
definitely counts.
Yes, but the effects of these deletions on lessening the bloat factor
are likely negligible. I believe it impossible to unbloat Emacs
without removing its greatest virtues. "The bloat stops here" is not
the credo I like all that much, unless I know exactly what is meant by
it.
We've been doing very well on the performance side.
True. Note, however, that 21.0 startup will be very slow -- slower
than 20.2, I think.
I've gotten kind of cranky in the last couple of weeks as my
nose
has been pushed in the fact that XEmacs 21.0 is going to really
suck.
I am still optimistic, except for the packages. They are problematic.
--
Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
You have an unusual magnetic personality. Don't walk too close to
metal objects which are not fastened down.