From: Didier <didibus@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 32471@debbugs.gnu.org
Subject: bug#32471: 26.1; ispell throwing wrong-type-argument stringp nil on Windows 10, with emacs 26.1 and hunspell
Date: Fri, 24 Aug 2018 14:30:58 -0700 [thread overview]
Message-ID: <CAMpjXycUFvYnCyX1SM7d6L4hMOQiw+LS=7yRmhVdQ_2TkjpRpA@mail.gmail.com> (raw)
In-Reply-To: <83h8jlb3sr.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 960 bytes --]
Bug can be closed.
It's not really a bug per say, just that hunspell must have a dictionary
for your exact locale. Even if you have en_US dictionary, if your locale is
ENU, it won't work. So make sure you have a dictionary of that exact name,
that is, <locale>.aff and <locale>.dic in your hunspell dictionary folder,
and all will work again.
Thanks for helping me out with this issue.
On Thu, 23 Aug 2018 at 06:39 Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Didier <didibus@gmail.com>
> > Date: Wed, 22 Aug 2018 20:31:13 -0700
> > Cc: 32471@debbugs.gnu.org
> >
> > Wow, that worked.
>
> OK, so can this bug be closed? Or is there something else left to do
> about it?
>
> > So, is there no way I can change my Locale within Emacs prior to loading
> ispell?
>
> There is, but why would you want to do that?
>
> Anyway, there's set-locale-environment. But beware: it changes quite
> a few of locale-related settings, so it might not be what you want.
>
[-- Attachment #2: Type: text/html, Size: 1467 bytes --]
next prev parent reply other threads:[~2018-08-24 21:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-18 7:11 bug#32471: 26.1; ispell throwing wrong-type-argument stringp nil on Windows 10, with emacs 26.1 and hunspell Didier
2018-08-18 18:35 ` Eli Zaretskii
2018-08-18 19:09 ` Eli Zaretskii
2018-08-20 8:12 ` Didier
2018-08-20 14:46 ` Eli Zaretskii
2018-08-23 3:31 ` Didier
2018-08-23 13:39 ` Eli Zaretskii
2018-08-24 21:30 ` Didier [this message]
2018-08-25 6:54 ` 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='CAMpjXycUFvYnCyX1SM7d6L4hMOQiw+LS=7yRmhVdQ_2TkjpRpA@mail.gmail.com' \
--to=didibus@gmail.com \
--cc=32471@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 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.