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

Previous Next

Package: emacs;

Reported by: dinkonin <dinkonin <at> gmail.com>

Date: Thu, 29 Oct 2020 21:41:02 UTC

Severity: normal

Found in version 28.0.50

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


Message #49 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: 44318 <at> debbugs.gnu.org, dinkonin <at> gmail.com
Subject: Re: bug#44318: 28.0.50;
 Problem with ispell/flyspell and ""enchant"" backend
Date: Mon, 02 Nov 2020 17:43:27 +0200
> From: Reuben Thomas <rrt <at> sc3d.org>
> Date: Mon, 2 Nov 2020 08:35:13 +0000
> Cc: dinkonin <dinkonin <at> gmail.com>, 44318 <at> 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.




This bug report was last modified 4 years and 293 days ago.

Previous Next


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