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

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#24435: closed (25.1; Problem using Hunspell)
Date: Fri, 16 Sep 2016 08:35:01 +0000

[Message part 1 (text/plain, inline)]

Your message dated Fri, 16 Sep 2016 11:34:24 +0300
with message-id <83bmzo5jlb.fsf <at> gnu.org>
and subject line Re: bug#24435: 25.1; Problem using Hunspell
has caused the debbugs.gnu.org bug report #24435,
regarding 25.1; Problem using Hunspell
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
24435: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=24435
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Dmitri Paduchikh <dpaduchikh <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: 25.1; Problem using Hunspell
Date: Wed, 14 Sep 2016 18:24:24 +0500

Hello,

Judging from ispell.el it should work with Hunspell, so I tried to use
it. But attempts to check a word produce the following error message.

| Starting new Ispell process hunspell with ru_RU dictionary...
| hunspell release 3.1.12 or greater is required (ispell-check-version)

The latest version of Hunspell is 1.4.1 as can be seen here:
https://github.com/hunspell/hunspell/releases

As I understand, the problem arises because ispell-check-version finds
version information using regexp

"(but really Hunspell \\([0-9]+\\.[0-9\\.-]+\\)?)"

The output of hunspell -vv does not match it, hence the results.

$ hunspell -vv < /dev/null
Hunspell 1.4.0
$ 

Best regards
Dmitri Paduchikh

In GNU Emacs 25.1.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.20.9)
 of 2016-09-09 built on nocturne.localdomain

[Message part 3 (message/rfc822, inline)]

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

> From: Dmitri Paduchikh <dpaduchikh <at> gmail.com>
> Cc: npostavs <at> users.sourceforge.net,  24435 <at> debbugs.gnu.org
> Date: Fri, 16 Sep 2016 13:06:59 +0500
> 
> >> $ 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.

Thanks, I'm therefore closing this bug report.

Previous Next

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