unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Reuben Thomas <rrt@sc3d.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:34:52 +0200	[thread overview]
Message-ID: <83k0dxpo5f.fsf@gnu.org> (raw)
In-Reply-To: <CAOnWdoje+jyTcPUrK5szPywcKjrrAKzp2FktQuFjPddMdiXS0Q@mail.gmail.com> (message from Reuben Thomas on Sun, 13 Feb 2022 21:33:32 +0000)

> From: Reuben Thomas <rrt@sc3d.org>
> Date: Sun, 13 Feb 2022 21:33:32 +0000
> Cc: Lars Ingebrigtsen <larsi@gnus.org>, 20741@debbugs.gnu.org
> 
>  Maybe we should have a list of exceptions?
> 
> As an upstream spellchecker maintainer, I don't think that's a good idea. Emacs should just be using the
> spellchecker. If it's not working, the problem should be fixed in the spellchecker.

I don't think I understand what this means in practice.  "Use the
spell-checker" how?  Do you mean we should not break words on
punctuation characters, or do you mean not to break them only on '.',
or do you mean something else?

Emacs is widely used to edit program sources, where stuff like
"file.attribute" and "list-my-packages" happens quite frequently.
Right now, these are not marked as misspellings, but if we pass them
to the speller with the punctuation, we are likely to get back
indications of misspelled words, which is not what we want.  Thus my
questions above: if we want to handle punctuation characters smarter
than just considering them part of the NOT-CASECHARS class, we need to
come up with a specification that will improve the situation, not make
it worse.  Can we do that?

> To be honest, I'm not sure Emacs can do much here.

I tend to agree, but maybe we can come up with some minor
improvements, even if they don't solve the problem in its entirety.





  parent reply	other threads:[~2022-02-14 13:34 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 [this message]
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=83k0dxpo5f.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=20741@debbugs.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).