unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: stefan@marxist.se, 23097@debbugs.gnu.org
Subject: bug#23097: 24.5; ispell.el: lines with both CASECHARS and NOT-CASECHARS get sent to the spell checker
Date: Wed, 14 Oct 2020 22:20:08 +0300	[thread overview]
Message-ID: <32dfc219-ac9c-8d9a-3140-d23977c8836c@gmail.com> (raw)
In-Reply-To: <83mu0q132o.fsf@gnu.org>

The whole ispell-dictionary-alist structure implies that matching would 
be done word by word. And looking into the dictionary setup is the first 
thing ispell.el user would do. Apart from NOT-CASECHARS it also has this 
element:

> OTHERCHARS is a regexp of characters in the NOT-CASECHARS set but 
> which can be
> used to construct words in some special way.  If OTHERCHARS characters 
> follow
> and precede characters from CASECHARS, they are parsed as part of a word,
> otherwise they become word-breaks...
Basically presence of both NOT-CASECHARS and OTHERCHARS implies that 
ispell.el does strict word by word matching. If we're just sending any 
line that contains a CASECHARS match, we don't really need either of 
them, since we can just match by CASECHARS alone and then send the line.

Oh, and there's another thing. Ispell.el actually does word by word 
search, but only on resume. Try my recipe again, just make the last line 
of spellchecked buffer to look like "doh kat". Then suspend the 
spellcheck after the first line and resume it with C-u M-$. You'd see 
that it skips the last line "doh" fine in this scenario. But then it 
suffers from the word mix problem described by Eli: spellchecking
dohkat" and "katdoh" results in kat alone being sent.

Thinking a bit more about this word mix problem, seems like it's not as 
simple to fix it as I thought in my previous letter, since we need some 
list of legitimate word separators for each language.

-- 
Best Regards,
Nikolay Kudryavtsev






      parent reply	other threads:[~2020-10-14 19:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-23 18:11 bug#23097: 24.5; ispell.el: lines with both CASECHARS and NOT-CASECHARS get sent to the spell checker Nikolay Kudryavtsev
2016-03-23 18:22 ` Eli Zaretskii
2016-03-23 20:12   ` Nikolay Kudryavtsev
2020-08-15  4:22   ` Stefan Kangas
2020-08-15 16:15     ` Eli Zaretskii
2020-08-15 16:40       ` Stefan Kangas
2020-08-17  9:20         ` Nikolay Kudryavtsev
2020-08-17 12:48           ` Stefan Kangas
2020-08-17 16:40           ` Eli Zaretskii
     [not found]             ` <08f3ac29-761c-ced7-1e2f-0f643512b986@gmail.com>
2020-10-13 17:00               ` Eli Zaretskii
     [not found]               ` <83mu0q132o.fsf@gnu.org>
2020-10-14 19:20                 ` Nikolay Kudryavtsev [this message]

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=32dfc219-ac9c-8d9a-3140-d23977c8836c@gmail.com \
    --to=nikolay.kudryavtsev@gmail.com \
    --cc=23097@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=stefan@marxist.se \
    /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).