all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Agustin Martin <agustin6martin@gmail.com>
To: 24435@debbugs.gnu.org, Dmitri Paduchikh <dpaduchikh@gmail.com>
Subject: bug#24435: 25.1; Problem using Hunspell
Date: Thu, 15 Sep 2016 15:41:23 +0200	[thread overview]
Message-ID: <20160915134123.4mxa3cukzybd7w6d@agmartin.aq.upm.es> (raw)
In-Reply-To: <83a8fa8mfy.fsf@gnu.org>

On Wed, Sep 14, 2016 at 07:40:01PM +0300, Eli Zaretskii wrote:
> > From: Dmitri Paduchikh <dpaduchikh@gmail.com>
> > Date: Wed, 14 Sep 2016 18:24:24 +0500
> > 
> > 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
> > $ 
> 
> They've changed the output in backward-incompatible ways.  Previous
> versions responded thusly:
> 
>   @(#) International Ispell Version 3.2.06 (but really Hunspell 1.3.2)
> 
> Since this change breaks backward compatibility, does that mean
> Hunspell is no longer compatible with the Ispell-like interface that
> Emacs expects?

Hi,

I have been looking at hunspell git repo, 

https://github.com/hunspell/hunspell

That string is defined in src/tools/hunspell.cxx file (line 60,
HUNSPELL_PIPE_HEADING) and seems to still be there. No changes in it
since end of last January, and they were only formatting changes.

With hunspell-1.4.1 in Debian GNU/Linux (note that 1.4.0 version is wrong),

$ hunspell -vv < /dev/null
@(#) International Ispell Version 3.2.06 (but really Hunspell 1.4.0)

$ hunspell -a < /dev/null
@(#) International Ispell Version 3.2.06 (but really Hunspell 1.4.0)

Although by the way,

$ hunspell -va < /dev/null
Hunspell 1.4.0
$ hunspell -vva < /dev/null
Hunspell 1.4.0

Where does your hunspell come from?

Regards,

-- 
Agustin





  reply	other threads:[~2016-09-15 13:41 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
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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160915134123.4mxa3cukzybd7w6d@agmartin.aq.upm.es \
    --to=agustin6martin@gmail.com \
    --cc=24435@debbugs.gnu.org \
    --cc=dpaduchikh@gmail.com \
    /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.