GNU bug report logs - #29801
25.3; ispell cannot detect installed dictionaries

Previous Next

Package: emacs;

Reported by: basilio <at> gmx.com

Date: Thu, 21 Dec 2017 16:29:01 UTC

Severity: normal

Merged with 31724

Found in versions 24.5, 25.3

Fixed in version 26.0.91

Done: Glenn Morris <rgm <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Tomas Nordin <tomasn <at> posteo.net>
To: Basilio <basilio <at> gmx.com>, Eli Zaretskii <eliz <at> gnu.org>
Cc: 29801 <at> debbugs.gnu.org
Subject: bug#29801: 25.3; ispell cannot detect installed dictionaries
Date: Fri, 22 Dec 2017 00:15:03 +0100
Basilio <basilio <at> gmx.com> writes:

> Eli Zaretskii <eliz <at> gnu.org> writes:
>
>>> From: Basilio <basilio <at> gmx.com>
>>> Cc: 29801 <at> debbugs.gnu.org
>>> Date: Thu, 21 Dec 2017 21:35:11 +0200
>>> 
>>> > Finally, what is the Aspell version?  What does "aspell -vv" produce?
>>> ~ % aspell -vv                         
>>> @(#) International Ispell Version 3.1.20 (but really Aspell 0.60.7-rc1)
>>
>> That's the problem, I think: that "-rc1" at the end of the version
>> string.  Emacs looks for a version string with this regexp:
>>
>>  (search-forward-regexp "(but really Aspell \\([0-9]+\\.[0-9\\.-]+\\)?)" nil t)
>>
>> which doesn't match 0.60.7-rc1.
>
> Thanks a lot!
>
> Is there an easy way to solve it on my level and chances that there will be some
> solution developed upstream? I'm not very proficient in Lisp unfortunately.

Sorry for just jumping in here out of the blue, but an ugly hack could
be to just add a ? in the end of the expression after the last ) in
ispell.el.

Find the code

(search-forward-regexp "(but really Aspell \\([0-9]+\\.[0-9\\.-]+\\)?)" nil t)

in ispell.el and add ? to the regexp string like this:

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

This makes it not require the ending paren and should (partly) match

     (but really Aspell 0.60.7-rc1)

The group match becomes 0.60.7-

(version<= "0.60" "0.60.7-")
(ispell-check-minver "0.6" "0.60.7-")

those both evaled to t without making problems for me.

If this is not too stupid to suggest (as a temporary home-fix) then
maybe someone could suggest a proper way of installing the hack.




This bug report was last modified 6 years and 352 days ago.

Previous Next


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