From: "André A. Gomes" <andremegafone@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 52331@debbugs.gnu.org, pogonyshev@gmail.com
Subject: bug#52331: M-$ doesn't respect subword mode
Date: Mon, 06 Dec 2021 17:21:28 +0000 [thread overview]
Message-ID: <87mtldy7hj.fsf@gmail.com> (raw)
In-Reply-To: <83h7bl1y1r.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 06 Dec 2021 18:46:24 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> However, and the Emacs maintainers will probably agree, the
>> responsibility of sending the "right" word to the ispell sub-process
>> should be on Emacs' side. I.e., when subword-mode is on, there should
>> be a call to word-at-point before sending it to the spell checker.
>
> It's not that easy, unfortunately. ispell.el has its own rules for
> what is a word, and the rules aren't static, they are determined
> dynamically by the definition of the dictionary. That's because of at
> least 2 reasons: (1) the rules must match what the dictionary
> considers a word, and (2) spell-checking is expected to work in
> buffers that mix several languages, so the rules need to be sensitive
> to the language of the dictionary and reject "words" whose letters are
> not part of the language.
Correct, my comment was over simplistic. But I don't see where my
reasoning fails. I can't think of an example where calling
word-at-point before the ispell rules kick in would make harm. What am
I missing?
> So perhaps a better approach is to teach subword-mode about the word
> rules of ispell.el, not the other way around. Patches welcome.
I don't see how this could help. Care to expand a bit?
--
André A. Gomes
"Free Thought, Free World"
next prev parent reply other threads:[~2021-12-06 17:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 15:09 bug#52331: M-$ doesn't respect subword mode Paul Pogonyshev
2021-12-06 16:34 ` André A. Gomes
2021-12-06 16:46 ` Eli Zaretskii
2021-12-06 17:21 ` André A. Gomes [this message]
2021-12-06 17:45 ` Eli Zaretskii
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=87mtldy7hj.fsf@gmail.com \
--to=andremegafone@gmail.com \
--cc=52331@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=pogonyshev@gmail.com \
/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).