From: Reuben Thomas via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, 20741@debbugs.gnu.org
Subject: bug#20741: 24.4; flyspell doesn't work with abbreviations ending in a period
Date: Mon, 14 Feb 2022 15:27:54 +0000 [thread overview]
Message-ID: <CAOnWdoiUzYecuS2CqZvPR6MsWdj_5C2yy-DdGWVM2sbj9DJCbA@mail.gmail.com> (raw)
In-Reply-To: <83ee45pj7r.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 975 bytes --]
On Mon, 14 Feb 2022 at 15:21, Eli Zaretskii <eliz@gnu.org> wrote:
>
> It's the same case: references to variables and other symbols in
> comments and strings of a program are very frequent. They are also
> very frequent in email messages which discuss programming, such as
> this discussion (I have Flyspell turned on in all my email buffers).
>
I think we can distinguish 3 different problems here:
1. Natural language spellchecking. That's what this issue is about.
2. Spell-checking code. (Essentially, identifiers.)
3. Finding code inside natural language, and checking it as if it were
code. (That's what you're talking about here.) This is not a spellchecking
problem, it's a problem of identifying which spell-checking apparatus to
use, rather like font-lock for multi-language buffers. It's hard to see how
to do it without some syntactic clue (e.g. the use of backticks in
markdown), as used in multi-language buffers for font-locking.
--
https://rrt.sc3d.org
[-- Attachment #2: Type: text/html, Size: 1957 bytes --]
next prev parent reply other threads:[~2022-02-14 15:27 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
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 [this message]
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=CAOnWdoiUzYecuS2CqZvPR6MsWdj_5C2yy-DdGWVM2sbj9DJCbA@mail.gmail.com \
--to=bug-gnu-emacs@gnu.org \
--cc=20741@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.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).