Tim Connors writes:
On Sat, 5 Jan 2008, Stephen J. Turnbull wrote:
> Unfortunately, Debian's policies concerning this kind of
> are a compromise, and in this kind of case they don't work very
> well with XEmacs.
I understand why they backport things, but do you know why they
link in the flyspell.el into both the emacs and xemacs trees, when both
the emacs (emacs22-el and emacs22-common) and xemacs (xemacs21-basesupport
and xemacs21-basesupport-el) packages have their own versions?
No, that sounds like a genuine bug and a violation of Debian's Emacs
> I'll try to remember to put "sync flyspell" on the
I am a little confused. On a Centos 4 machine where I have not been able
to break flyspell at all, the flyspell.el is dating from 2002.
Well, obviously somebody thought flyspell needed some changes since
there's a fairly large diff from 2002 to 2007. If you can't break
the 2002 version, don't worry about it (unless we break things by
The reporter obviously never solved that bug, instead getting a
self-consistent version of the sumo instead of debian's version. Despite
being basically the same file in Centos4, the button-2 fault does not
appear in it.
Sounds like Debian has other patches somewhere that cause the problem.
So I installed flyspell.el (v 1.7n) from
and it seems to be working perfectly on debian, it having overridden the
version in xemacs21-basesupport, and of course the one in
dictionaries-common. That's where I am now -- using upstream's 1.7n
version on debian, and am not going to touch the Centos4 machine until it
Nice to know. Sounds like you are set, and like we can update to a
much more recent version without causing anyone too much pain.
Thanks for the followup, and a happy, productive 2008 to you!
XEmacs-Beta mailing list