unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Reuben Thomas <rrt@sc3d.org>
Cc: tor.kringeland@ntnu.no, 52179@debbugs.gnu.org
Subject: bug#52179: Highlighting a word in `ispell' using `enchant'
Date: Wed, 25 May 2022 05:28:46 +0300	[thread overview]
Message-ID: <83tu9e4a75.fsf@gnu.org> (raw)
In-Reply-To: <CAOnWdohqoDULLrZq3XDqbOnTkusPiJzG7FYw8STOJHwLYsiOZQ@mail.gmail.com> (message from Reuben Thomas on Tue, 24 May 2022 22:34:14 +0100)

> From: Reuben Thomas <rrt@sc3d.org>
> Date: Tue, 24 May 2022 22:34:14 +0100
> Cc: Tor Kringeland <tor.kringeland@ntnu.no>, 52179@debbugs.gnu.org
> 
> Since ispell is the only spellchecker Emacs supports that can't cope with [[:alpha:]], it would seem more
> sensible to have a default (nil-keyed) setting in ispell-dictionary-base-alist, and to overwrite the default with
> [A-Za-z] only if the spellchecker is really ispell.
> 
> This way, duplicate code can be removed and future spellcheckers will not need to rediscover this problem.

That might be okay, but how does it help us get the Enchant support in
ispell.el DTRT?  We'd still need to detect when Ispell is used as the
back-end speller, no?

The issue here is that the current code already "patches" the nil case
to use [:alpha:] when Aspell or Hunspell are the spell-checker, and we
need to do that for Enchant.  If you are saying that Enchant doesn't
need to worry about the Ispell case, we could just modify
ispell-find-enchant-dictionaries to always "patch" the nil entry to
use [:alpha:], and leave the rest of the code, which already works,
intact.  If Enchant does need to cater to Ispell, we need a more
complex change, but again it's local th the Enchant support code.





  reply	other threads:[~2022-05-25  2:28 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
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 [this message]
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=83tu9e4a75.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).