From: Agustin Martin <agustin6martin@gmail.com>
To: 24435@debbugs.gnu.org
Cc: Dmitri Paduchikh <dpaduchikh@gmail.com>, npostavs@users.sourceforge.net
Subject: bug#24435: 25.1; Problem using Hunspell
Date: Thu, 15 Sep 2016 17:22:01 +0200 [thread overview]
Message-ID: <20160915152200.wr5hndsrb2fznqtr@agmartin.aq.upm.es> (raw)
In-Reply-To: <83k2ed6y0a.fsf@gnu.org>
On Thu, Sep 15, 2016 at 05:25:25PM +0300, Eli Zaretskii wrote:
> > From: Dmitri Paduchikh <dpaduchikh@gmail.com>
> > Cc: npostavs@users.sourceforge.net, 24435@debbugs.gnu.org
> > Date: Thu, 15 Sep 2016 01:10:29 +0500
> >
> > > Also, can you look (in 'ps' or some similar system utility) what is
> > > the exact command line that Emacs invokes Hunspell in your case?
> >
> > It was
> >
> > $ pgrep -a hunspell
> > 5897 /usr/bin/hunspell -d ru_RU -i UTF-8
> >
> > After this I have added "-a" to ispell-extra-args and now it seems to be
> > working.
>
> How did it happen that Hunspell was invoked without the -a switch,
> though? AFAICS, ispell-start-process hard-codes the -a switch, so it
> should have been invoked with it.
I think it is ispell-call-process what is used for this particular purpose
by ispell-check-version. No -a seems used here.
--
Agustin
next prev parent reply other threads:[~2016-09-15 15:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 13:24 bug#24435: 25.1; Problem using Hunspell Dmitri Paduchikh
2016-09-14 13:46 ` Noam Postavsky
2016-09-14 15:33 ` Dmitri Paduchikh
2016-09-14 16:57 ` Eli Zaretskii
2016-09-14 17:44 ` Dmitri Paduchikh
2016-09-14 18:50 ` Eli Zaretskii
2016-09-14 20:10 ` Dmitri Paduchikh
2016-09-15 14:25 ` Eli Zaretskii
2016-09-15 15:22 ` Agustin Martin [this message]
2016-09-15 16:20 ` Eli Zaretskii
2016-09-15 17:36 ` Agustin Martin
2016-09-15 20:59 ` Dmitri Paduchikh
2016-09-16 6:29 ` Eli Zaretskii
2016-09-16 8:06 ` Dmitri Paduchikh
2016-09-16 8:34 ` Eli Zaretskii
2016-09-14 16:40 ` Eli Zaretskii
2016-09-15 13:41 ` Agustin Martin
2016-09-15 21:42 ` Dmitri Paduchikh
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=20160915152200.wr5hndsrb2fznqtr@agmartin.aq.upm.es \
--to=agustin6martin@gmail.com \
--cc=24435@debbugs.gnu.org \
--cc=dpaduchikh@gmail.com \
--cc=npostavs@users.sourceforge.net \
/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).