bug#32319: 27.0.50; flyspell-mode error on start

[Eric Abrahamsen]

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Eric Abrahamsen <eric@ericabrahamsen.net>
>> Date: Mon, 30 Jul 2018 12:42:24 -0700
>> 
>> 
>> Turning on flyspell-mode started giving me an error a few days ago, on
>> two different machines I use. Both are Arch linux, both running Emacs
>> master.
>> 
>> My only ispell customizations:
>> 
>> (setq ispell-program-name (executable-find "hunspell"))
>> (setq ispell-personal-dictionary "~/.aspell.en_US.pws")
>> 
>> Starting flyspell-mode gives me:
>> 
>> Debugger entered--Lisp error: (wrong-type-argument stringp nil)
>>   string-match("," nil 0)
>>   split-string(nil "," t)
>>   ispell-parse-hunspell-affix-file(nil)
>>   ispell-hunspell-fill-dictionary-entry(nil)
>>   ispell-start-process()
>>   ispell-init-process()
>>   ispell-buffer-local-words()
>>   ispell-accept-buffer-local-defs()
>>   flyspell-accept-buffer-local-defs(force)
>>   flyspell-mode-on()
>> 
>> >From "emacs -Q", setting `ispell-program-name' to (executable-find
>> "hunspell") (the first line of my customizations above) is sufficient to
>> trigger the error.
>
> You mean, just evaluating
>
>   (setq ispell-program-name (executable-find "hunspell"))
>
> signals an error??

No, sorry, I meant setting the program name to "hunspell" and then doing
anything spelling-related caused an error.

But! This was a false alarm: the problem is a bug in the hunspell_en
package for Arch linux, which is missing some symlinks, and causing
several other programs to fail: 

https://bugs.archlinux.org/task/59401

It might have been nice if ispell allowed the real error to reach me
(during edebugging I did see something like "no affix file found for
"en_US""), but I suppose it isn't a big deal.

Eric