From: Alexander Shukaev <haroogan@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 19229@debbugs.gnu.org
Subject: bug#19229: ispell-phaf: No matching entry for ...
Date: Sun, 30 Nov 2014 22:55:17 +0100 [thread overview]
Message-ID: <CAKu-7Wxf1sDyWsnHOTKJn8_O6zC7ci-LTNpv3ScofdpHNVCKeQ@mail.gmail.com> (raw)
In-Reply-To: <83mw788k5w.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 3797 bytes --]
Thanks a lot for the tip.
I don't know what was wrong with MSYS2 version of hunspell, but this one
works with the following minimal configuration:
(setq ispell-program-name (executable-find "hunspell"))
(setq ispell-local-dictionary "en_US")
(setq ispell-local-dictionary-alist '(("en_US"
"[[:alpha:]]"
"[^[:alpha:]]"
"[']"
nil
nil
nil
utf-8)))
Nevertheless, I can still see
ispell-phaf: No matching entry for nil
So it still tries to call `ispell-parse-hunspell-affix-file' with `nil' for
the first time, and only then calls it with "en_US" in my case.
Secondly, I think that relying on "hunspell -D" so stubbornly that
`ispell-parse-hunspell-affix-file' blocks all further usage of ispell.el
with hunspell if `ispell-hunspell-dict-paths-alist' is just dumb. Here are
a few reasons:
1. Not all distributions of hunspell even supply "share/hunspell/*"
stuff with them;
2. Some users don't use dictionaries from "share/hunspell/*" because
they might get either more updated dictionaries themselves and/or already
have customized personal dictionaries.
For instance, #2 is exactly what I was planning to do:
(let ((dictionaries-dir (expand-file-name "dictionaries"
user-emacs-directory)))
(make-directory dictionaries-dir t)
(setq ispell-local-dictionary "en_US")
(setq ispell-local-dictionary-alist '((nil
"[[:alpha:]]"
"[^[:alpha:]]"
"[']"
nil
("-d" "en_US"
"-p" dictionaries-dir)
nil
utf-8)
("en_US"
"[[:alpha:]]"
"[^[:alpha:]]"
"[']"
nil
("-d" "en_US"
"-p" dictionaries-dir)
nil
utf-8)
("german"
"[[:alpha:]]"
"[^[:alpha:]]"
"[']"
t
("-d" "de_DE_frami"
"-p" dictionaries-dir)
"~tex"
utf-8)
("russian"
"[[:alpha:]]"
"[^[:alpha:]]"
"[']"
nil
("-d" "ru_RU"
"-p" dictionaries-dir)
nil
utf-8)))))
and in this case I obviously don't care at all whether hunspell has
anything in "share/hunspell/*" or not. So why would I be forcefully blocked
to use it with some weird error from `ispell-parse-hunspell-affix-file'?
How about redesign?
[-- Attachment #2: Type: text/html, Size: 8878 bytes --]
next prev parent reply other threads:[~2014-11-30 21:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-30 18:25 bug#19229: ispell-phaf: No matching entry for Alexander Shukaev
2014-11-30 19:50 ` bug#19229: A workaround for hunspell Chris Zheng
2014-12-01 16:26 ` Eli Zaretskii
2014-11-30 21:15 ` bug#19229: ispell-phaf: No matching entry for Eli Zaretskii
2014-11-30 21:55 ` Alexander Shukaev [this message]
2014-12-01 16:24 ` Eli Zaretskii
2014-12-01 17:15 ` Alexander Shukaev
2015-05-20 18:53 ` bug#19229: ispell on Windows Alan Third
2015-05-20 19:21 ` Eli Zaretskii
2015-05-20 20:34 ` Alan Third
2015-05-21 2:41 ` Eli Zaretskii
2015-05-21 8:16 ` Alan Third
2015-05-21 16:23 ` Eli Zaretskii
2015-05-21 20:19 ` Alan Third
2015-05-22 6:53 ` Eli Zaretskii
2015-05-22 18:57 ` Alan Third
2015-05-22 19:22 ` Eli Zaretskii
2015-05-22 19:55 ` Alan Third
2015-05-22 20:08 ` Eli Zaretskii
2015-05-22 21:46 ` Jan D.
2020-09-07 21:55 ` Lars Ingebrigtsen
2020-09-07 22:08 ` Alan Third
2020-09-08 10:12 ` Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKu-7Wxf1sDyWsnHOTKJn8_O6zC7ci-LTNpv3ScofdpHNVCKeQ@mail.gmail.com \
--to=haroogan@gmail.com \
--cc=19229@debbugs.gnu.org \
--cc=eliz@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).