From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: emacs ispell error on windows10 with hunspell
Date: Sun, 03 May 2020 18:05:23 +0300 [thread overview]
Message-ID: <83wo5toy8c.fsf@gnu.org> (raw)
In-Reply-To: <CAE5V+8GRfH=pS4DFoySoeHjVGTLc0=sd-pJi-vyAEx=vu2O+bQ@mail.gmail.com> (message from 刘虎 on Sun, 3 May 2020 12:07:52 +0800)
> From: 刘虎 <richardliu.sdlw@gmail.com>
> Date: Sun, 3 May 2020 12:07:52 +0800
>
> Inspired by your answer,I think my problem may be caused by the wrong
> placement of hunspell dictionary files, so I copied the dictionary
> files " en_US.aff"
> and "en_US.dic " to the dictionary C:/Hunspell. And I retyped hunspell -D
> in cmd and get the following reply:
> [image: image.png]
If you read the error message carefully, you will see that Hunspell
complains about the "default" dictionary, not about the en_US
dictionary. So you should copy en_US.dic to default.dic and en_US.aff
to default.aff in the same C:\Hunspell directory, and your problem
should be solved.
> Debugger entered--Lisp error: (error
> "D:/Install/hunspell/src/tools/hunspell.exe did not output version line")
> signal(error ("D:/Install/hunspell/src/tools/hunspell.exe did not output
> version line"))
What does the following display, if you type the command from the
Windows cmd.exe shell prompt?
D:\Install\hunspell\src\tools\hunspell.exe -vv
next prev parent reply other threads:[~2020-05-03 15:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-03 4:07 emacs ispell error on windows10 with hunspell 刘虎
2020-05-03 15:05 ` Eli Zaretskii [this message]
[not found] ` <CAE5V+8EQWZPCz2-r1h=-Jj+fd0_ap7Xb51jyLWUmvx759Up5PA@mail.gmail.com>
2020-05-04 14:48 ` Eli Zaretskii
[not found] ` <CAE5V+8FF7YWRR1LT3y9XZnpu2aHZc1kKbfoqLgpxoT-64uSO9A@mail.gmail.com>
2020-05-05 14:19 ` Eli Zaretskii
2020-05-04 0:23 ` Robert Thorpe
-- strict thread matches above, loose matches on Subject: below --
2020-04-30 16:06 Richard LIU
2020-04-30 17:40 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83wo5toy8c.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.