From: Eli Zaretskii <eliz@gnu.org>
To: Reuben Thomas <rrt@sc3d.org>
Cc: dinkonin@gmail.com, 44318@debbugs.gnu.org
Subject: bug#44318: 28.0.50; Problem with ispell/flyspell and ""enchant"" backend
Date: Mon, 02 Nov 2020 17:43:27 +0200 [thread overview]
Message-ID: <838sbjepcw.fsf@gnu.org> (raw)
In-Reply-To: <CAOnWdoj_CVNSgPqszX3k-FRc+JNpSiNa13_RKyOzS50rG+33iA@mail.gmail.com> (message from Reuben Thomas on Mon, 2 Nov 2020 08:35:13 +0000)
> From: Reuben Thomas <rrt@sc3d.org>
> Date: Mon, 2 Nov 2020 08:35:13 +0000
> Cc: dinkonin <dinkonin@gmail.com>, 44318@debbugs.gnu.org
>
> I believe that the ispell.el code (which I wrote) is buggy: it should not be incorporating warnings into its
> output.
>
> Also, the patch I offered is a simplification of the original code. So, I don't think we are losing here.
>
> Eli, I quite agree with your sentiment, and I would certainly not advocate installing a workaround in Emacs
> unless there were compelling reasons. However, I do not see this as a workaround, and as it is also a
> simplification, I don't see a problem.
I have a problem with ignoring stderr because it can provide some
useful information. Moreover, no one said that some client of
Enchant, current or future, won't decide to produce non-error output
on stderr.
Sorry.
next prev parent reply other threads:[~2020-11-02 15:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 20:25 bug#44318: 28.0.50; Problem with ispell/flyspell and ""enchant"" backend dinkonin
2020-10-30 7:38 ` Eli Zaretskii
2020-10-30 22:56 ` Reuben Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-10-31 7:29 ` Eli Zaretskii
2020-10-31 7:32 ` dinkonin
2020-10-31 7:50 ` Eli Zaretskii
2020-10-31 8:37 ` dinkonin
2020-10-31 9:17 ` Eli Zaretskii
2020-11-01 22:23 ` Reuben Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-02 3:34 ` Eli Zaretskii
2020-11-02 8:14 ` dinkonin
2020-11-02 15:41 ` Eli Zaretskii
2020-11-02 8:35 ` Reuben Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-02 15:41 ` dinkonin
2020-11-02 15:43 ` Eli Zaretskii [this message]
2020-11-02 15:49 ` Reuben Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-02 16:10 ` Eli Zaretskii
2020-11-02 21:49 ` Reuben Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-03 16:45 ` Eli Zaretskii
2020-11-03 17:06 ` Reuben Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <CAOnWdohVdcVffjvptfJUjhRr1jdNn7H3PBzon0LvrR_cguPPow@mail.gmail.com>
[not found] ` <835z6mcqyg.fsf@gnu.org>
2020-11-03 17:19 ` Reuben Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-03 17:31 ` Eli Zaretskii
2020-11-03 18:27 ` Reuben Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-03 18:50 ` Eli Zaretskii
2020-11-03 18:53 ` Reuben Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-03 19:39 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=838sbjepcw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=44318@debbugs.gnu.org \
--cc=dinkonin@gmail.com \
--cc=rrt@sc3d.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).