On Fri, Jan 04, 2008 at 09:49:41PM +1100, Tim Connors wrote:
> Package: dictionaries-common
> Version: 0.90.0
> Severity: normal
> 
> As far as I can work out, dictionaries-common owns the symlinks in
> /usr/share/xemacs21/site-lisp/dictionaries-common/ to flyspell.el etc.

It is actually the .elc there what is loaded, but that should make no
difference

> This links to a emacs version from 2007 that is unfortunately not
> completely compatible with xemacs.  If I blast those links and the
> .elc files away, xemacs uses its own version from 2002, in 
> /usr/share/xemacs21/xemacs-packages/lisp/text-modes/flyspell.elc
> from the xemacs21-basesupport package.

The 2007 version is the one from emacs cvs patched to work with xemacs21
and emacs21. While I tried to find all problems seems that some of them got
missed (e.g., #458806). 

> The symptoms of the incompatibility that I see are that flyspell-mode
> is no longer a minor mode.  If I invoke M-x flyspell-mode, it invokes
> it for all buffers (including programs and shell scripts that are
> pointless to spell check, and flyspell-mode ends up invoking bogus
> font-locking on keywords).  It even invokes it for commands and
> filenames I enter in the modeline.

I can confirm this, but looking at the code, 2007 flyspell.el uses
(easy-mmode) define-minor-mode which, according to the documentation should
preserve the buffer-local character of the mode unless explicitly asked
otherwise.

I will try to look at easy-mmode, in case I am missing something there. Of
course, since I am not fully familiar with the xemacs internals, help is
more than welcome.

> Please either remove the symlinks, or make this version work in
> xemacs, and get the xemacs21-basesupport maintainer to remove their
> version of flyspell.

I am largely for making the version work everywhere if possible. While I
can always wrap the old definition into a huge (if (featurep 'xemacs) ... )
I would prefer a cleaner fix.

Thanks for your report. Feel free to provide more feedback.

-- 
Agustin



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to