GNU bug report logs -
#33493
26.1; New Version of Hunspell (1.7.0-1) brakes ispell.el
Previous Next
Reported by: Philipp Uhl <philipp.uhl <at> rwth-aachen.de>
Date: Sat, 24 Nov 2018 23:45:02 UTC
Severity: normal
Merged with 33606
Found in version 26.1
Fixed in version 26.2
Done: Eli Zaretskii <eliz <at> gnu.org>
Bug is archived. No further changes may be made.
Full log
Message #11 received at 33493 <at> debbugs.gnu.org (full text, mbox):
Yes, it appears to resolve the issue.
Thank you very much, best regards
Philipp
On 25.11.18 17:10, Eli Zaretskii wrote:
>> From: Philipp Uhl <philipp.uhl <at> rwth-aachen.de>
>> Date: Sun, 25 Nov 2018 00:17:02 +0100
>>
>> After the update from hunspell 1.6.2-1 to 1.7.0-1 the ispell package
>> printed the following messages:
>>
>> Starting new Ispell process hunspell with en_US dictionary...
>> Setting up indent for shell type zsh
>> Indentation variables are now local.
>> Indentation setup for shell type zsh
>> Error in post-command-hook (flyspell-post-command-hook): (error "No data
>> for dictionary \"en_US\" in ‘ispell-local-dictionary-alist’ or
>> ‘ispell-dictionary-alist’")
>>
>> I checked and ispell-local-dictionary-alist and ispell-dictionary-alist
>> are both nil.
>>
>> Consequently my hunspell setup did't work but the error occures on
>> running (ispell).
> This is due to an incompatible change in Hunspell, for a reason that
> looks entirely arbitrary to me: Hunspell will now show the LOADED
> DICTIONARY header (which ispell.el expects and on which it depends)
> only if there's at least one file argument on the command line. Why
> they made that change is anybody's guess.
>
> Does the patch below resolve the problem?
>
> diff --git a/lisp/textmodes/ispell.el b/lisp/textmodes/ispell.el
> index e77bc7e..9789968 100644
> --- a/lisp/textmodes/ispell.el
> +++ b/lisp/textmodes/ispell.el
> @@ -1113,7 +1113,12 @@ ispell-find-hunspell-dictionaries
> null-device
> t
> nil
> - "-D")
> + ;; Hunspell 1.7.0 (and later?) won't
> + ;; show LOADED DICTIONARY unless
> + ;; there's at least one file argument
> + ;; on the command line. So we feed
> + ;; it with the null device.
> + "-D" null-device)
> (buffer-string))
> "[\n\r]+"
> t))
This bug report was last modified 6 years and 170 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.