[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Eric Abrahamsen
Subject: bug#32319: 27.0.50; flyspell-mode error on start
Date: Sat, 04 Aug 2018 22:21:47 -0700
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux)

Eli Zaretskii <address@hidden> writes:

>> From: Eric Abrahamsen <address@hidden>
>> Cc: address@hidden
>> Date: Wed, 01 Aug 2018 12:51:54 -0700
>> If the symlink is not present, the "hunspell -D" output looks like:
>> SEARCH PATH:.:: <elided>
>> /usr/share/hunspell/en_TT
>> <more>
>> Can't open affix or dictionary files for dictionary named "en_US".
>> IOW, there's no line that matches "\\.aff$", and
>> `hunspell-default-dictionary' is never set, and the error is raised in
>> line 1177, where it's assumed that that variable has a value.
>> So things go wrong pretty early on, as soon as Hunspell fails to load a
>> dictionary.
> Does the patch below produce a useful diagnostic?

This patch is just fine, and would certainly be a lot better than the
current situation. I only note that, if we allow this function to fail
silently, the error you get *later on*, when you try to use flyspell to
do something, comes directly from hunspell and says exactly what the
problem is (ie, which dictionary it tried and failed to load). That's
even more helpful. If we did that, this function could just call
`ispell-print-if-debug' and log the failure quietly.

But raising an error directly is also fine, and might be preferable in
order to avoid creating weird problems further down the line.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]