From: Eli Zaretskii <eliz@gnu.org>
To: "Paul W. Rankin" <hello@paulwrankin.com>
Cc: 39483@debbugs.gnu.org
Subject: bug#39483: 27.0.60; ispell ignores syntax/category tables word boundaries
Date: Fri, 07 Feb 2020 20:23:33 +0200 [thread overview]
Message-ID: <83r1z6dzoa.fsf@gnu.org> (raw)
In-Reply-To: <m2blqa4d1n.fsf@paulwrankin.com> (hello@paulwrankin.com)
> From: "Paul W. Rankin" <hello@paulwrankin.com>
> Date: Sat, 08 Feb 2020 01:44:52 +1000
>
> It appears that the function `ispell-get-word' makes its own judgements
> on word boundaries, ignoring the buffer's syntax tables and character
> categories.
That is true. And I don't really see how it can be any different,
since ispell.el must have the same notion of a word as the underlying
dictionary, otherwise you will have false positives and/or false
negatives, right?
ispell.el looks up the word characters and non-word characters in
its database, and the doc string of ispell-dictionary-base-alist
explains how.
> This becomes a problem with using `electric-quote-mode' and
> ispell, because contractions are parsed as separate words. e.g. Calling
> ispell word for "doesn’t" returns:
>
> T is correct
>
> To reproduce:
>
> 1. emacs -Q
> 2. (in *scratch*) M-x text-mode RET
> 3. enter text "doesn’t" (i.e. "doesn" C-x 8 ] "t")
> 4. M-: (modify-syntax-entry ?’ "w")
> 5. M-: (modify-category-entry ?’ ?^)
> 6. M-$ | ispell-word
The buffer syntax table has no effect on ispell.el, and shouldn't have
any effect on it.
> Attempts at workarounds:
>
> I've tried altering slot 3 of the corresponding `ispell-dictionary-base-alist'
> entries from "[']" to "['’]" to no avail.
That's the right direction, but you didn't follow it far enough.
First, ispell-dictionary-base-alist is the default value, and is used
to produce ispell-dictionary-alist, which is one you should change
(alternatively, customize ispell-local-dictionary-alist). More
importantly, the definitions of each dictionary include more than just
one character set: there are 3 character sets there and one parameter
for encoding the string passed to the spell-checker, and you should be
sure to set them all as appropriate for the dictionary you use.
My suggestion is to step with Edebug through ispell-get-word and see
why it doesn't consider "doesn’t" as a single word in your case.
> Setup:
>
> GNU Emacs 27.0.60 (build 2, x86_64-apple-darwin19.3.0, NS appkit-1894.30
> Version 10.15.3 (Build 19D76)) of 2020-02-05
This omits crucial information, like the dictionary in use and the
locale-dependent settings that affect encoding. (In any case, I don't
think this list is the right place of discussing this issue.)
next prev parent reply other threads:[~2020-02-07 18:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 15:44 bug#39483: 27.0.60; ispell ignores syntax/category tables word boundaries Paul W. Rankin
2020-02-07 18:23 ` Eli Zaretskii [this message]
2020-02-08 5:47 ` Paul W. Rankin
2020-02-08 8:18 ` Eli Zaretskii
2020-02-08 9:28 ` Paul W. Rankin
2020-02-08 10:06 ` 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=83r1z6dzoa.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=39483@debbugs.gnu.org \
--cc=hello@paulwrankin.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).