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

Previous Next

Full log

Message #53 received at 24435 <at> debbugs.gnu.org (full text, mbox):

From: Dmitri Paduchikh <dpaduchikh <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 24435 <at> debbugs.gnu.org, npostavs <at> users.sourceforge.net
Subject: Re: bug#24435: 25.1; Problem using Hunspell
Date: Fri, 16 Sep 2016 13:06:59 +0500

Hello,

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

>> 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?

You are right. It is my own script which I wrote away back with some
obscure purpose and did not remove.

$ cat `which hunspell`
#!/bin/sh
shift
exec /usr/bin/hunspell "$@"

After removing this script, unmodified ispell.el works as expected.
Sorry for false alarm.

Best regards
Dmitri Paduchikh

Previous Next

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