From: Eli Zaretskii <eliz@gnu.org>
To: dinkonin <dinkonin@gmail.com>, Reuben Thomas <rrt@sc3d.org>
Cc: 44318@debbugs.gnu.org
Subject: bug#44318: 28.0.50; Problem with ispell/flyspell and ""enchant"" backend
Date: Fri, 30 Oct 2020 09:38:28 +0200 [thread overview]
Message-ID: <83k0v8b1u3.fsf@gnu.org> (raw)
In-Reply-To: <CANqWMH9=V1SuPFp-+pih4uQJ=0vabpo-yMn4eEW_sMmUseoprQ@mail.gmail.com> (message from dinkonin on Thu, 29 Oct 2020 22:25:47 +0200)
> From: dinkonin <dinkonin@gmail.com>
> Date: Thu, 29 Oct 2020 22:25:47 +0200
>
> I'm having some trouble with flyspell using the enchant backend
> (setq ispell-program-name "enchant-2").
>
> I have installed the latest enchant 2.2.12, without the
> optional finish and hebrew backends. Flyspell refuses to work with the
> above setting (no errors just does not detect anything ). Ive
> narrowed it down to this:
>
> when flyspell loads it adds the following line n top of "ispell-enchant-dictionary-alist"
>
> ((nil "[[:alpha:]]" "[^[:alpha:]]" "[\n** (process:98935): WARNING **:
> 22:05:56.283: Error loading plugin: libvoikko.so.1: cannot open shared
> object file: No such file or directory\n\n\n** (process:98935): WARNING
> **: 22:05:56.286: Error loading plugin: libhspell.so.0: cannot open
> shared object file: No such file or directory\n\n0123456789]" t nil nil
> utf-8)
These look like local configuration problems on your system, or some
bug in Enchant: it tells you that some shared libraries are missing.
> I've noticed that enchant-lsmod-2 also produces this error in the
> terminal, maybe STDERR should be omitted when generating
> ispell-enchant-dictionary-alist or shoud this be reported upstream to
> enchant ?
The latter, I think. Reuben, can you please comment?
next prev parent reply other threads:[~2020-10-30 7:38 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 [this message]
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
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=83k0v8b1u3.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 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.