GNU bug report logs - #44318
28.0.50; Problem with ispell/flyspell and ""enchant"" backend

Previous Next

Full log

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Reuben Thomas <rrt <at> sc3d.org>
Cc: dinkonin <at> gmail.com, 44318 <at> debbugs.gnu.org
Subject: Re: bug#44318: 28.0.50;
 Problem with ispell/flyspell and ""enchant"" backend
Date: Tue, 03 Nov 2020 21:39:40 +0200

> From: Reuben Thomas <rrt <at> sc3d.org>
> Date: Tue, 3 Nov 2020 18:53:54 +0000
> Cc: 44318 <at> debbugs.gnu.org, dinkonin <dinkonin <at> gmail.com>
> 
>  We are miscommunicating.  My point is that if Emacs will depend on
>  Enchant and won't be able to use the existing spellers without Enchant
>  being in-between, then we will be in a dire situation if Enchant stops
>  being developed and bit-rots.  By contrast, with the current code, we
>  can always tell users to use aspell/hunspell directly.
> 
> What I was trying to say is that it would be very easy to re-add support for the other spell-checkers, since
> they and Enchant operate in the same way, and they would not have changed in the mean time.

If we switch to supporting only Enchant, the compatibility will soon
disappear.  And re-adding back deleted code is just waste of
resources.  So I still think this is not a good idea, sorry.

> in the end it should be less effort to maintain Enchant than to
> maintain multiple back-ends in ispell.el.

That's an advantage, indeed, but as I said before, the downsides
overwhelm it.

Previous Next

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