all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Arash Esbati <arash@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Hunspell 1.6 on Msys2
Date: Wed, 18 Jan 2017 22:05:59 +0200	[thread overview]
Message-ID: <83shog6sm0.fsf@gnu.org> (raw)
In-Reply-To: <86bmv4m9e2.fsf@gnu.org> (message from Arash Esbati on Wed, 18 Jan 2017 20:54:29 +0100)

> From: Arash Esbati <arash@gnu.org>
> Cc: emacs-devel@gnu.org
> Date: Wed, 18 Jan 2017 20:54:29 +0100
> 
> > Actually, one other idea: do you have any LC_* variables in the
> > environment?  (MinGW programs shouldn't pay attention, but maybe
> > MinGW64/MSYS2 guys did something so they do.)
> 
> Many thanks for taking your time and checking!  locale returns:
> 
> LANG=en_US.UTF-8
> LC_CTYPE="en_US.UTF-8"
> LC_NUMERIC="en_US.UTF-8"
> LC_TIME="en_US.UTF-8"
> LC_COLLATE="en_US.UTF-8"
> LC_MONETARY="en_US.UTF-8"
> LC_MESSAGES="en_US.UTF-8"
> LC_ALL=
> 
> Do you have other settings?

Is this in the MSYS Bash?  I meant inside Emacs.

I have none of these.  Windows runtime ignores these variables, but
maybe MSYS2 Hunspell doesn't.  What happens if you set LC_ALL=C and
try your recipe again?



  reply	other threads:[~2017-01-18 20:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-17 22:16 Hunspell 1.6 on Msys2 Arash Esbati
2017-01-18  3:38 ` Eli Zaretskii
2017-01-18 10:22   ` Arash Esbati
2017-01-18 15:35     ` Eli Zaretskii
2017-01-18 17:57       ` Arash Esbati
2017-01-18 18:20         ` Eli Zaretskii
2017-01-18 18:39           ` Arash Esbati
2017-01-18 19:15             ` Eli Zaretskii
2017-01-18 19:19               ` Eli Zaretskii
2017-01-18 19:54                 ` Arash Esbati
2017-01-18 20:05                   ` Eli Zaretskii [this message]
2017-01-19  9:04                     ` Arash Esbati
2017-01-19 15:56                       ` Eli Zaretskii
2017-01-20  8:54                         ` Arash Esbati

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=83shog6sm0.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=arash@gnu.org \
    --cc=emacs-devel@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.