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: Mon, 02 Nov 2020 18:10:46 +0200 Message-ID: <83y2jjd9ix.fsf@gnu.org> References: <83k0v8b1u3.fsf@gnu.org> <83o8ki96m6.fsf@gnu.org> <83k0v6hhzg.fsf@gnu.org> <83h7q8e8ja.fsf@gnu.org> <838sbjepcw.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="21857"; mail-complaints-to="usenet@ciao.gmane.io" Cc: dinkonin@gmail.com, 44318@debbugs.gnu.org To: Reuben Thomas Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Nov 02 17:12:10 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 1kZcRG-0005YS-5P for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 02 Nov 2020 17:12:10 +0100 Original-Received: from localhost ([::1]:34600 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kZcRE-0002EC-T8 for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 02 Nov 2020 11:12:08 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:38946) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kZcR8-0002E2-PU for bug-gnu-emacs@gnu.org; Mon, 02 Nov 2020 11:12:02 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:59009) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kZcR8-0006fY-G3 for bug-gnu-emacs@gnu.org; Mon, 02 Nov 2020 11:12:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1kZcR8-0008PG-Bl for bug-gnu-emacs@gnu.org; Mon, 02 Nov 2020 11:12: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: Mon, 02 Nov 2020 16:12: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.160433346332246 (code B ref 44318); Mon, 02 Nov 2020 16:12:02 +0000 Original-Received: (at 44318) by debbugs.gnu.org; 2 Nov 2020 16:11:03 +0000 Original-Received: from localhost ([127.0.0.1]:42322 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kZcQA-0008O2-Pe for submit@debbugs.gnu.org; Mon, 02 Nov 2020 11:11:03 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:38542) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kZcQ9-0008NS-IS for 44318@debbugs.gnu.org; Mon, 02 Nov 2020 11:11:01 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:49238) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kZcQ4-0006YV-79; Mon, 02 Nov 2020 11:10:56 -0500 Original-Received: from [176.228.60.248] (port=3300 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1kZcQ3-0000pK-MP; Mon, 02 Nov 2020 11:10:56 -0500 In-Reply-To: (message from Reuben Thomas on Mon, 2 Nov 2020 15:49:19 +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:192544 Archived-At: > From: Reuben Thomas > Date: Mon, 2 Nov 2020 15:49:19 +0000 > Cc: dinkonin , 44318@debbugs.gnu.org > > So I, as upstream maintainer, am telling you that indeed, it is not correct that Emacs should take > enchant-lsmod's stderr as part of its output! (As I said above, it would be possible to capture stderr > separately and display it to the user, though I don't recommend that currently, because the warnings are not > written for users. Other programs that use Enchant do not show these warnings, they simply omit providers > that do not load from the list of languages/spelling checkers that are available.) OK, I agree to this change, under protest.