From: Stefan Kangas <stefan@marxist.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: sw9@outlook.com, 25825@debbugs.gnu.org
Subject: bug#25825: 25.1; ispell-find-hunspell-dictionaries not working on Windows
Date: Wed, 26 Aug 2020 13:10:13 -0700 [thread overview]
Message-ID: <CADwFkmmqVQ5n+BGuXi=pKVj8mD4vf5Qx3bcPJjEgqrfz8q+11Q@mail.gmail.com> (raw)
In-Reply-To: <83eent2o36.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
>> But for some reason, hunspell is very sensitive and will not give any
>> loaded dictionary if $LANG is unset. (IMO, very unhelpful behaviour.)
>
> Maybe this is worth a bug report against Hunspell.
I filed a bug report against hunspell here:
https://github.com/hunspell/hunspell/issues/687
> But is this really relevant to how Hunspell is invoked from Emacs? It
> certainly isn't on Windows, because we inject LANG into the
> environment there. But what about Posix hosts?
AFAIU, we just inherit the environment such that if $LANG is unset in
the parent process,
(getenv "LANG") => nil
> That cannot fly: we cannot second-guess the user's locale, and we
> shouldn't force some arbitrary locale on them. It's basically a
> mis-configured system, so signaling an error is good enough, IMO.
Point taken.
next prev parent reply other threads:[~2020-08-26 20:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 3:41 bug#25825: 25.1; ispell-find-hunspell-dictionaries not working on Windows S W
2020-08-26 18:09 ` Stefan Kangas
2020-08-26 18:28 ` Eli Zaretskii
2020-08-26 18:34 ` Eli Zaretskii
2020-08-27 4:32 ` Stefan Kangas
2020-11-24 8:43 ` Lars Ingebrigtsen
2020-08-26 18:36 ` Eli Zaretskii
2020-08-26 18:48 ` Stefan Kangas
2020-08-26 18:59 ` Eli Zaretskii
2020-08-26 19:21 ` Stefan Kangas
2020-08-26 19:39 ` Eli Zaretskii
2020-08-26 20:10 ` Stefan Kangas [this message]
2020-08-26 20:01 ` Stefan Kangas
2020-08-27 3:27 ` Eli Zaretskii
2020-08-27 3:51 ` Stefan Kangas
2020-08-26 18:48 ` Stefan Kangas
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='CADwFkmmqVQ5n+BGuXi=pKVj8mD4vf5Qx3bcPJjEgqrfz8q+11Q@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=25825@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=sw9@outlook.com \
/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.