bug#7272: 24.0.50; Enabling Flyspell mode gave an error

[Agustin Martin]

On Sun, Oct 24, 2010 at 10:23:38AM +0800, jidanni@jidanni.org wrote:
> >>>>> "EZ" == Eli Zaretskii <eliz@gnu.org> writes:
> >> From: jidanni@jidanni.org
> >> Date: Sun, 24 Oct 2010 04:21:47 +0800
> >> Cc: rfrancoise@debian.org
> >> 
> >> $ emacs -Q /etc/motd -nw -f flyspell-mode
> >> Enabling Flyspell mode gave an error
> 
> EZ> How about showing that error message?  (No, I don't see any errors
> EZ> with today's bzr.)
> 
> One can see it in the minibuffer and with view-echo-area-messages C-h e:
> ("emacs" "/etc/motd" "-f" "flyspell-mode")
> For information about GNU Emacs and the GNU system, type C-h C-a.
> Note: file is write protected
> Starting new Ispell process [default] ...
> Enabling Flyspell mode gave an error

Cannot reproduce that here,

$ emacs -Q /etc/motd -nw -f flyspell-mode
("emacs" "/etc/motd" "-f" "flyspell-mode")
For information about GNU Emacs and the GNU system, type C-h C-a.
Note: file is write protected
Starting new Ispell process [default] ...

No errors. Same with the X variant,

$ emacs -Q /etc/motd -f flyspell-mode

Glenn Morris has committed a change to make flyspell show what is the error
when flyspell.el finds an error. That should already be included in last
emacs-snapshot Debian package prepared by Romain Francoise (emacs-snapshot
1:20101024-1). Can you try with that newer emacs-snapshot, so we have more 
info about the problem?

> Maybe a Debian guy can confirm it.

Note that Debian emacs-snapshot package uses pristine spellchecking files 
from FSF Emacs bzr repo, no Debian specific changes are applied.

Thanks for your feedback,

-- 
Agustin