From: Eli Zaretskii <eliz@gnu.org>
To: Reuben Thomas <rrt@sc3d.org>
Cc: 20741@debbugs.gnu.org
Subject: bug#20741: 24.4; flyspell doesn't work with abbreviations ending in a period
Date: Sat, 06 Jun 2015 13:03:36 +0300 [thread overview]
Message-ID: <834mmlnog7.fsf@gnu.org> (raw)
In-Reply-To: <CAOnWdojMU=5s5MQYi-RYKHW5xc8FWa3Jar233628u1XOzzuJ+w@mail.gmail.com>
> Date: Sat, 6 Jun 2015 10:38:17 +0100
> From: Reuben Thomas <rrt@sc3d.org>
> Cc: 20741@debbugs.gnu.org
>
> I should add, if I M-x ispell-change-dictionary
> RET american RET, then allow the underlining to refresh, "etc." is no longer
> marked as wrong (as we've seen, it's incorrectly in the "american" word list),
> but "i.e." and "e.g." are still so marked.
That's not what I see here. When en_US is used, neither of these is
flagged as a mis-spelling. When I switch to en_GB, only "etc" and the
"i" in "i.e." are flagged, the rest (including all of "e.g.") are not.
I guess the reason is the different versions of Hunspell dictionaries
we have installed.
Once again, I don't think this is an Emacs problem. Don't you see the
same when you invoke Hunspell as a stand-alone program?
next prev parent reply other threads:[~2015-06-06 10:03 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-05 14:06 bug#20741: 24.4; flyspell doesn't work with abbreviations ending in a period Reuben Thomas
2015-06-05 14:08 ` bug#20741: Workaround Reuben Thomas
2015-06-05 19:23 ` bug#20741: 24.4; flyspell doesn't work with abbreviations ending in a period Eli Zaretskii
2015-06-05 21:42 ` Reuben Thomas
2015-06-06 6:49 ` Eli Zaretskii
2015-06-06 9:35 ` Reuben Thomas
2015-06-06 9:38 ` Reuben Thomas
2015-06-06 10:03 ` Eli Zaretskii [this message]
2015-06-06 10:08 ` Reuben Thomas
2015-06-06 10:11 ` Reuben Thomas
2015-06-06 10:36 ` Eli Zaretskii
2015-06-06 9:58 ` Eli Zaretskii
2022-02-13 9:04 ` Lars Ingebrigtsen
2022-02-13 12:37 ` Eli Zaretskii
2022-02-13 21:33 ` Reuben Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-14 10:44 ` Lars Ingebrigtsen
2022-02-14 13:08 ` martin rudalics
2022-02-14 15:28 ` Reuben Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-14 13:34 ` Eli Zaretskii
2022-02-14 13:43 ` Reuben Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-14 15:07 ` Stephen Berman
2022-02-14 15:21 ` Eli Zaretskii
2022-02-14 15:27 ` Reuben Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-14 16:42 ` Eli Zaretskii
2022-02-14 17:01 ` Reuben Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-14 18:08 ` martin rudalics
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=834mmlnog7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=20741@debbugs.gnu.org \
--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 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).