From: Eli Zaretskii <eliz@gnu.org>
To: Tor Kringeland <tor.kringeland@ntnu.no>, Reuben Thomas <rrt@sc3d.org>
Cc: 52179@debbugs.gnu.org
Subject: bug#52179: Highlighting a word in `ispell' using `enchant'
Date: Tue, 24 May 2022 22:36:27 +0300 [thread overview]
Message-ID: <83v8tu4tac.fsf@gnu.org> (raw)
In-Reply-To: <OL1P279MB0194FC1704121BEF4382383088D79@OL1P279MB0194.NORP279.PROD.OUTLOOK.COM> (message from Tor Kringeland on Tue, 24 May 2022 19:27:58 +0000)
> From: Tor Kringeland <tor.kringeland@ntnu.no>
> CC: "52179@debbugs.gnu.org" <52179@debbugs.gnu.org>
> Date: Tue, 24 May 2022 19:27:58 +0000
>
> Aspell works for me, but enchant doesn't. When I change `ispell-program-name' to "aspell" ispell starts recognizing full words.
>
> Looking into the functions you mentioned, it seems like `ispell-find-aspell-dictionaries' explicitly adds an entry for nil, while `ispell-find-enchant-dictionaries' doesn't. This is what causes the bug for me since I have set `ispell-dictionary' to nil/haven't changed it so the resulting regex recognizing words is too strict for my use.
Then maybe ispell-find-enchant-dictionaries should be improved?
> Might there be a reason why `ispell-find-enchant-dictionaries' doesn't set a nil entry? For sure I would think it could handle whatever input aspell can.
I don't know. CC'ing Reuben, who might know better.
next prev parent reply other threads:[~2022-05-24 19:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-29 14:44 bug#52179: Highlighting a word in `ispell' using `enchant' Tor Kringeland
2021-11-29 14:51 ` Eli Zaretskii
2021-11-29 20:46 ` Tor Kringeland
2021-11-30 3:22 ` Eli Zaretskii
2022-05-24 15:49 ` Tor Kringeland
2022-05-24 19:11 ` Eli Zaretskii
2022-05-24 19:27 ` Tor Kringeland
2022-05-24 19:36 ` Eli Zaretskii [this message]
2022-05-24 21:34 ` Reuben Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-25 2:28 ` Eli Zaretskii
2022-05-25 7:39 ` Reuben Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-25 13:23 ` Eli Zaretskii
2022-05-27 13:45 ` Tor Kringeland
2022-05-27 14:22 ` 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=83v8tu4tac.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=52179@debbugs.gnu.org \
--cc=rrt@sc3d.org \
--cc=tor.kringeland@ntnu.no \
/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).