unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.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: Sun, 13 Feb 2022 10:04:38 +0100	[thread overview]
Message-ID: <87o83bxhll.fsf@gnus.org> (raw)
In-Reply-To: <CAOnWdoiyUFF1cVo8m82BURE7UCgCumAAF-=NrA4vNCUpAYT1YA@mail.gmail.com> (Reuben Thomas's message of "Sat, 6 Jun 2015 10:35:46 +0100")

[-- Attachment #1: Type: text/plain, Size: 537 bytes --]

Reuben Thomas <rrt@sc3d.org> writes:

> 1. Rename my ~/.hunspell_en_GB.
>
> 2. Start "emacs -Q"
>
> 3. M-x flyspell-mode RET
>
> 4. M-x customize-variable RET ispell-program-name RET; set to "/usr/bin/hunspell"
> (doing this after step 3 because the variable is not available for customization
> before loading ispell)
>
> 5. Type "etc. i.e. e.g."
>
> All of the above is now red-underwiggled.

Easier reproduction case:

----
(setq ispell-program-name "/usr/bin/hunspell")
(ispell-change-dictionary "en_GB")
(flyspell-mode)

etc.
----


[-- Attachment #2: Type: image/png, Size: 1830 bytes --]

[-- Attachment #3: Type: text/plain, Size: 57 bytes --]


Note red wiggle under etc.  `M-$' on the etc gives me:


[-- Attachment #4: Type: image/png, Size: 6429 bytes --]

[-- Attachment #5: Type: text/plain, Size: 221 bytes --]


So flyspell doesn't really understand that a full stop can be part of a
word, apparently?  (This is with Emacs 29.)

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

  parent reply	other threads:[~2022-02-13  9:04 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
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 [this message]
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=87o83bxhll.fsf@gnus.org \
    --to=larsi@gnus.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).