From: dinkonin <dinkonin@gmail.com>
To: Reuben Thomas <rrt@sc3d.org>
Cc: 44318@debbugs.gnu.org
Subject: bug#44318: 28.0.50; Problem with ispell/flyspell and ""enchant"" backend
Date: Mon, 2 Nov 2020 17:41:11 +0200 [thread overview]
Message-ID: <CANqWMH-q7s6iYmwMhEXhuJBcfoxsRgd9BvtQ2y-gBg5aHkwiPg@mail.gmail.com> (raw)
In-Reply-To: <CAOnWdoj_CVNSgPqszX3k-FRc+JNpSiNa13_RKyOzS50rG+33iA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1423 bytes --]
Thanks you Reuben Thomas, I hope this gets resolved in the best way
possible,
Unfortunately Arch maintainers have declined looking at this with the
following Catch 22 comment:
>> FS#68499 - [enchant] Warnings about optional dependencies.>> Reason for
closing: Not a bug
>> Additional comments about closing: Warnings are not errors. If emacs
Flyspell doesn't work upon seeing enchant *warnings*, Flyspell should be
fixed
As for me, I think I will refrain from reporting more bugs for now.
Be safe.
On Mon, Nov 2, 2020 at 10:35 AM Reuben Thomas <rrt@sc3d.org> wrote:
> On Mon, 2 Nov 2020 at 03:34, Eli Zaretskii <eliz@gnu.org> wrote:
>
>>
>> Thanks, but I'm not interested in working around installation problems
>> of programs we invoke. It's a slippery slope, with never-ending
>> additional requests we will have to honor.
>>
>
> The reporter and I seem to have swapped positions on this!
>
> 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.
>
> --
> https://rrt.sc3d.org
>
[-- Attachment #2: Type: text/html, Size: 2889 bytes --]
next prev parent reply other threads:[~2020-11-02 15:41 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 [this message]
2020-11-02 15:43 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CANqWMH-q7s6iYmwMhEXhuJBcfoxsRgd9BvtQ2y-gBg5aHkwiPg@mail.gmail.com \
--to=dinkonin@gmail.com \
--cc=44318@debbugs.gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.