From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: jorge+list@disroot.org, 42248@debbugs.gnu.org
Subject: bug#42248: 27.0.91; With enchant-2.2.8 from Guix, Flyspell errors out or gives lots of false positives
Date: Thu, 27 Aug 2020 20:49:07 +0300 [thread overview]
Message-ID: <83d03c0yjw.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmk-DBAV_5G2S6PhAOZueXZ=LQV3xy7s90v+Js5rkFc4zQ@mail.gmail.com> (message from Stefan Kangas on Thu, 27 Aug 2020 10:30:00 -0700)
> From: Stefan Kangas <stefan@marxist.se>
> Date: Thu, 27 Aug 2020 10:30:00 -0700
> Cc: Eli Zaretskii <eliz@gnu.org>, 42248@debbugs.gnu.org
>
> Jorge P. de Morais Neto <jorge+list@disroot.org> writes:
>
> > However, both ispell-buffer and Flyspell still misreport "doesn't".
>
> I am using Hunspell and it misrepresents "doesn't" as a typo here, too.
It isn't the Hunspell issue, it's an issue with the dictionary. What
does your en_US.aff file says in the WORDCHARS line(s)? See the
function ispell-parse-hunspell-affix-file which parses the Hunspell
aff files.
On my system, there's no issue with "don't" (and the apostrophe in
general).
Eventually, the dictionary's entry in the ispell.el's DB is what
matters. What do you have there?
next prev parent reply other threads:[~2020-08-27 17:49 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 16:06 bug#42248: 27.0.91; With enchant-2.2.8 from Guix, Flyspell errors out or gives lots of false positives Jorge P. de Morais Neto
[not found] ` <CADwFkm=7Pus_bMhUita=70qsRjfRiNN+oe-YnsCucpParnfPcA@mail.gmail.com>
2020-08-20 1:35 ` Jorge P. de Morais Neto
2020-08-20 1:56 ` Jorge P. de Morais Neto
2020-08-20 13:18 ` Eli Zaretskii
2020-08-20 15:36 ` Jorge P. de Morais Neto
2020-08-20 16:02 ` Eli Zaretskii
2020-08-20 17:49 ` Jorge P. de Morais Neto
2020-08-20 17:52 ` Jorge P. de Morais Neto
2020-08-20 18:26 ` Eli Zaretskii
2020-08-22 20:54 ` Jorge P. de Morais Neto
2020-08-27 17:30 ` Stefan Kangas
2020-08-27 17:49 ` Eli Zaretskii [this message]
2020-08-27 19:05 ` Stefan Kangas
2020-08-27 19:13 ` Eli Zaretskii
2020-08-27 19:13 ` Eli Zaretskii
2020-08-24 14:30 ` Jorge P. de Morais Neto
2020-08-24 14:42 ` Eli Zaretskii
2020-08-30 18:51 ` Jorge P. de Morais Neto
2020-08-24 15:08 ` Stefan Kangas
2020-08-27 17:30 ` Stefan Kangas
2020-08-27 17:49 ` Eli Zaretskii
2020-08-27 19:05 ` Stefan Kangas
2020-08-27 19:14 ` Eli Zaretskii
2020-09-06 23:53 ` bug#42248: Problems between Flyspell and Enchant Reuben Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-07 15:48 ` Eli Zaretskii
2020-09-07 20:07 ` Reuben Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-07 21:20 ` Reuben Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-26 13:02 ` bug#42248: 27.0.91; With enchant-2.2.8 from Guix, Flyspell errors out or gives lots of false positives Lars Ingebrigtsen
2020-09-07 21:10 ` bug#42248: Problems between Flyspell and Enchant Reuben Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=83d03c0yjw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=42248@debbugs.gnu.org \
--cc=jorge+list@disroot.org \
--cc=stefan@marxist.se \
/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).