From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#44318: 28.0.50; Problem with ispell/flyspell and ""enchant"" backend Date: Tue, 03 Nov 2020 21:39:40 +0200 Message-ID: <83wnz2b56r.fsf@gnu.org> References: <83k0v8b1u3.fsf@gnu.org> <83o8ki96m6.fsf@gnu.org> <83k0v6hhzg.fsf@gnu.org> <83h7q8e8ja.fsf@gnu.org> <838sbjepcw.fsf@gnu.org> <83y2jjd9ix.fsf@gnu.org> <83a6vycru9.fsf@gnu.org> <835z6mcqyg.fsf@gnu.org> <834km6cpo2.fsf@gnu.org> <83zh3yb7hb.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="2168"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 44318@debbugs.gnu.org, dinkonin@gmail.com To: Reuben Thomas Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Nov 03 20:40:09 2020 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ka2A4-0000RM-MU for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 03 Nov 2020 20:40:08 +0100 Original-Received: from localhost ([::1]:35800 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ka2A3-0007Y5-O9 for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 03 Nov 2020 14:40:07 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:59870) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ka29y-0007Xw-Pj for bug-gnu-emacs@gnu.org; Tue, 03 Nov 2020 14:40:02 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:34955) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1ka29y-00084n-GO for bug-gnu-emacs@gnu.org; Tue, 03 Nov 2020 14:40:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ka29y-0003l9-Cz for bug-gnu-emacs@gnu.org; Tue, 03 Nov 2020 14:40:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 03 Nov 2020 19:40:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 44318 X-GNU-PR-Package: emacs Original-Received: via spool by 44318-submit@debbugs.gnu.org id=B44318.160443239414434 (code B ref 44318); Tue, 03 Nov 2020 19:40:02 +0000 Original-Received: (at 44318) by debbugs.gnu.org; 3 Nov 2020 19:39:54 +0000 Original-Received: from localhost ([127.0.0.1]:46501 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ka29q-0003kk-Ie for submit@debbugs.gnu.org; Tue, 03 Nov 2020 14:39:54 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:59732) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ka29o-0003kV-Oo for 44318@debbugs.gnu.org; Tue, 03 Nov 2020 14:39:53 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:50403) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ka29j-00082p-9g; Tue, 03 Nov 2020 14:39:47 -0500 Original-Received: from [176.228.60.248] (port=2052 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1ka29i-0000Ic-Jq; Tue, 03 Nov 2020 14:39:47 -0500 In-Reply-To: (message from Reuben Thomas on Tue, 3 Nov 2020 18:53:54 +0000) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:192644 Archived-At: > From: Reuben Thomas > Date: Tue, 3 Nov 2020 18:53:54 +0000 > Cc: 44318@debbugs.gnu.org, dinkonin > > 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.