From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Reuben Thomas via "Bug reports for GNU Emacs, the Swiss army knife of text editors" Newsgroups: gmane.emacs.bugs Subject: bug#44318: 28.0.50; Problem with ispell/flyspell and ""enchant"" backend Date: Tue, 3 Nov 2020 18:53:54 +0000 Message-ID: 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> Reply-To: Reuben Thomas Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000001dae9c05b3386352" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="1711"; mail-complaints-to="usenet@ciao.gmane.io" Cc: dinkonin , 44318@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Nov 03 19:55:25 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 1ka1Sm-0000AT-EC for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 03 Nov 2020 19:55:24 +0100 Original-Received: from localhost ([::1]:40160 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ka1Sl-0003Jb-Db for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 03 Nov 2020 13:55:23 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:50748) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ka1SQ-0003JH-Fl for bug-gnu-emacs@gnu.org; Tue, 03 Nov 2020 13:55:02 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:34867) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1ka1SQ-0002AL-68 for bug-gnu-emacs@gnu.org; Tue, 03 Nov 2020 13:55:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ka1SQ-0000RJ-4L for bug-gnu-emacs@gnu.org; Tue, 03 Nov 2020 13:55:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Reuben Thomas Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 03 Nov 2020 18:55: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.16044296531625 (code B ref 44318); Tue, 03 Nov 2020 18:55:02 +0000 Original-Received: (at 44318) by debbugs.gnu.org; 3 Nov 2020 18:54:13 +0000 Original-Received: from localhost ([127.0.0.1]:46413 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ka1Rd-0000Q9-57 for submit@debbugs.gnu.org; Tue, 03 Nov 2020 13:54:13 -0500 Original-Received: from mail-ot1-f48.google.com ([209.85.210.48]:35539) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ka1Rb-0000Pv-UC for 44318@debbugs.gnu.org; Tue, 03 Nov 2020 13:54:12 -0500 Original-Received: by mail-ot1-f48.google.com with SMTP id n11so16979554ota.2 for <44318@debbugs.gnu.org>; Tue, 03 Nov 2020 10:54:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sc3d.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=MPxlXeW0mr5kHFvFU9KFPjfcRTRCTyxihtVX9fulET8=; b=Z7Uq3Iw2x4oiaZNh2i3UGrnREZpHShTMmJMB5kYS70V4ZYU2wysMXnfTtDY63IOW6o D82GhZoWK8sdtqizq6Z6RwQDyIbztqIP2L+uokEcqAilVpieRhl/zIdGIbzaJ8s4GU37 5f4Y6ZkT9DO0etV4q2DxZEWdJ/TMNbV8APmfU= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=MPxlXeW0mr5kHFvFU9KFPjfcRTRCTyxihtVX9fulET8=; b=GygJZfB2wqeYFrqyfpmgBr+s74jSprv9p4MeChlsuyVHJN6U1qTva3wNXzkYNbfGqr Z1p5ht4GJGskmlmZi+OfDo+gvPlqBHwtu2chvoGjz2J5l509qR3hjzBhJhYXWIkZB33W OgyWIrauyelTV1LTevEWl3qThIljiY1bgCv/TbdkLsWI4e0ozBY6jLKaRvfutZTE1Uay E50saaYg3c+zvDCtVYCjG/Pppj7gJqNeJvNthP2Q3DnyS21KGidJPxoZkey7fFW5VuxP 2UTz0hqabQfQVq3x9KKIY6LOa5P7wo0+RCRZxh+W+s2XCi1g3tfZvYaqtq+q/S2oKP37 EOPg== X-Gm-Message-State: AOAM532xRfj2UBEKJvY3G2DmJ/Hj2zHSrQl6Ux43Bi2B5JQn5gvV7zi5 I3GI1hOQQVjzgEWdWGpD3KUynPlKXMp/4oRCegTLWg== X-Google-Smtp-Source: ABdhPJwWgRnu/+6YQEFISx3gwh+J5yieX3fJhMTZ/vksY9bjXUbBI21ilCX5BynfsEm2T6L842ZGw2VOkYA7XNt58Zo= X-Received: by 2002:a9d:6c4e:: with SMTP id g14mr1931765otq.120.1604429645956; Tue, 03 Nov 2020 10:54:05 -0800 (PST) In-Reply-To: <83zh3yb7hb.fsf@gnu.org> 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:192637 Archived-At: --0000000000001dae9c05b3386352 Content-Type: text/plain; charset="UTF-8" On Tue, 3 Nov 2020 at 18:50, Eli Zaretskii wrote: > > From: Reuben Thomas > > Date: Tue, 3 Nov 2020 18:27:32 +0000 > > Cc: 44318@debbugs.gnu.org, dinkonin > > > > I think it would be wrong for Emacs to do that, as that would put all > > the eggs in a single basket, something that is not safe in Free > > Software world, where packages become unmaintained outside of our > > control. > > > > I don't understand this: Emacs, to this day, is happy to import large > quantities of code from other project; let > > alone the option of forking/maintaining free software, which is one of > its great benefits. And because > > Enchant has such a similar interface to the other supported > spell-checkers, the cost of switching is low. For > > myself, I'd be more concerned with bugs or missing functionality in > Enchant as a reason to be cautious (i.e. > > I would want to see a phased transition) than about the long-term > prospects. > > 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. There is little to rot in Enchant, I intend to reduce that amount, and in the end it should be less effort to maintain Enchant than to maintain multiple back-ends in ispell.el. -- https://rrt.sc3d.org --0000000000001dae9c05b3386352 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Tue, 3 Nov 2020 at 18:50, Eli Zaretskii <eliz@gnu.org> wrote:
> From: Reuben Thomas <rrt@sc3d.org>
> Date: Tue, 3 Nov 2020 18:27:32 +0000
> Cc: 44318@d= ebbugs.gnu.org, dinkonin <dinkonin@gmail.com>
>
>=C2=A0 I think it would be wrong for Emacs to do that, as that would pu= t all
>=C2=A0 the eggs in a single basket, something that is not safe in Free<= br> >=C2=A0 Software world, where packages become unmaintained outside of ou= r
>=C2=A0 control.
>
> I don't understand this: Emacs, to this day, is happy to import la= rge quantities of code from other project; let
> alone the option of forking/maintaining free software, which is one of= its great benefits. And because
> Enchant has such a similar interface to the other supported spell-chec= kers, the cost of switching is low. For
> myself, I'd be more concerned with bugs or missing functionality i= n Enchant as a reason to be cautious (i.e.
> I would want to see a phased transition) than about the long-term pros= pects.

We are miscommunicating.=C2=A0 My point is that if Emacs will depend on
Enchant and won't be able to use the existing spellers without Enchant<= br> being in-between, then we will be in a dire situation if Enchant stops
being developed and bit-rots.=C2=A0 By contrast, with the current code, we<= br> 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 n= ot have changed in the mean time. There is little to rot in Enchant, I inte= nd to reduce that amount, and in the end it should be less effort to mainta= in Enchant than to maintain multiple back-ends in ispell.el.

--
--0000000000001dae9c05b3386352--