GNU bug report logs - #24435
25.1; Problem using Hunspell

Previous Next

Package: emacs;

Reported by: Dmitri Paduchikh <dpaduchikh <at> gmail.com>

Date: Wed, 14 Sep 2016 13:27:01 UTC

Severity: normal

Found in version 25.1

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Dmitri Paduchikh <dpaduchikh <at> gmail.com>
Cc: 24435 <at> debbugs.gnu.org, npostavs <at> users.sourceforge.net
Subject: bug#24435: 25.1; Problem using Hunspell
Date: Fri, 16 Sep 2016 09:29:12 +0300
> From: Dmitri Paduchikh <dpaduchikh <at> gmail.com>
> Cc: npostavs <at> users.sourceforge.net,  24435 <at> debbugs.gnu.org
> Date: Fri, 16 Sep 2016 01:59:58 +0500
> 
> > 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.
> 
> With ispell-extra-args being empty, the eventual form to start Hunspell is
> 
> * make-process(:name "ispell" :buffer nil :command ("hunspell" "-a" ""
>   "-d" "ru_RU" "-i" "UTF-8"))
> 
> However right after evaluation of this form pgrep shows this:
> 
> $ pgrep -a hunspell
> 6310 /usr/bin/hunspell  -d ru_RU -i UTF-8
> $ tr \\0 \\n < /proc/6310/cmdline | cat -n
>      1	/usr/bin/hunspell
>      2	
>      3	-d
>      4	ru_RU
>      5	-i
>      6	UTF-8
> $ 

Does it mean hunspell is a shell script, which omits the -a when it
invokes the actual program?  How else to explain the fact that -a
disappears?




This bug report was last modified 8 years and 251 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.