From: Eli Zaretskii <eliz@gnu.org>
To: Jorge P. de Morais Neto <jorge+list@disroot.org>
Cc: 42248@debbugs.gnu.org, stefan@marxist.se
Subject: bug#42248: 27.0.91; With enchant-2.2.8 from Guix, Flyspell errors out or gives lots of false positives
Date: Thu, 20 Aug 2020 19:02:31 +0300 [thread overview]
Message-ID: <83a6ypcnl4.fsf@gnu.org> (raw)
In-Reply-To: <87eeo1z5we.fsf@disroot.org> (message from Jorge P. de Morais Neto on Thu, 20 Aug 2020 12:36:01 -0300)
> From: Jorge P. de Morais Neto <jorge+list@disroot.org>
> Cc: stefan@marxist.se, 42248@debbugs.gnu.org
> Date: Thu, 20 Aug 2020 12:36:01 -0300
>
> > Do you see the same problem when you invoke Enchant from the shell
> > prompt?
>
> Yes, enchant-2 on the command line misreports numbers:
> $ enchant-2 -d en_US -l /tmp/enchant-test.txt
> 2015
> Casa
> 42
>
> $ enchant-2 -d pt_BR -l /tmp/enchant-test.txt
> doesn't
> 2015
> 42
Then I guess at least part of the problem is with Enchant (or the
Aspell back-end it uses), and not with Emacs.
> Therefore, the list for "american" specifies `("-B" #4="-d" "en_US")' as
> ISPELL-ARGS. However, enchant-2 does not take a "-B" flag:
>
> $ enchant-2 -B -d en_US /tmp/enchant-test.txt
> Usage: enchant-2 -a|-l|-h|-v [-L] [-d DICTIONARY] [FILE]
> -d DICTIONARY use the given dictionary
> -a list suggestions in ispell pipe mode format
> -l list only the misspellings
> -L display line numbers
> -h display help and exit
> -v display version information and exit
So instead of ignoring -B, Enchant reports an error -- another
incompatibility with Ispell, Aspell, and Hunspell.
>
> $ enchant-2 -B -d en_US -l /tmp/enchant-test.txt
> Usage: enchant-2 -a|-l|-h|-v [-L] [-d DICTIONARY] [FILE]
> -d DICTIONARY use the given dictionary
> -a list suggestions in ispell pipe mode format
> -l list only the misspellings
> -L display line numbers
> -h display help and exit
> -v display version information and exit
>
>
> Also, the list for "en_US" specifies "" for OTHERCHARS, but, IIUC, it
> ought to be "[']" instead.
This means something is wrong with the initialization, as the data is
set up correctly in ispell.el. Does the above happen in "emacs -Q"?
next prev parent reply other threads:[~2020-08-20 16:02 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 [this message]
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
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=83a6ypcnl4.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).