From: Eli Zaretskii <eliz@gnu.org>
To: Artem Boldarev <artem.boldarev@gmail.com>
Cc: 32280@debbugs.gnu.org
Subject: bug#32280: 26.1; FLYSPELL-BUFFER sometimes misbehaves for some input in a large enough buffer
Date: Fri, 27 Jul 2018 15:45:27 +0300 [thread overview]
Message-ID: <83bmassv88.fsf@gnu.org> (raw)
In-Reply-To: <992503e5-5f88-30c7-e9b9-fe0a884d2e52@gmail.com> (message from Artem Boldarev on Thu, 26 Jul 2018 12:44:26 +0300)
> From: Artem Boldarev <artem.boldarev@gmail.com>
> Date: Thu, 26 Jul 2018 12:44:26 +0300
>
> Checking large enough buffer with FlySpell leads to the unexpected
> results (at least, when spell checking Russian, but I believe that it is
> possible to reproduce the bug for other languages, at least Ukrainian).
>
> For example, when checking large enough buffer (large enough to trigger
> flyspell-large-region) I got the following messages in the *Messages*
> buffer:
>
> Local Ispell dictionary set to ru_RU
> Starting new Ispell process hunspell with ru_RU dictionary...
> Checking region...
> Spell Checking...100% [посимвольно]
> Spell Checking completed.
> -> смом - 346: word not found
> -> стостояния - 319: word not found
> -> рекрсивного - 308: word not found
> -> универсальнее - 266: word not found
> -> генериует - 222: word not found
>
> It was not able to find the misspelt words to highlight them in the
> buffer which I tried
> to spell check. On the other hand, some not misspelt words were
> highlighted (именно,
> бесконечный, усложняет). Under other circumstances, these words are not
> highlighted as misspelt (which is as it should be).
Can you post the text where this happens?
> The problem turned out to be in the flyspell-external-point-words: It
> makes some heuristic checks before calling (flyspell-word nil t). It
> seems that these checks are OK for English, as I never encountered any
> problems when spell-checking English texts.
>
> Here is the version of the function which seems to be correct:
AFAICT, you have removed a single line:
(< found-length misspell-length)
Can you take me through your reasoning why this line is incorrect, and
what assumptions it made that are correct for English, but not for
Russian?
Thanks.
next prev parent reply other threads:[~2018-07-27 12:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-26 9:44 bug#32280: 26.1; FLYSPELL-BUFFER sometimes misbehaves for some input in a large enough buffer Artem Boldarev
2018-07-27 12:45 ` Eli Zaretskii [this message]
2018-07-28 0:00 ` Artem Boldarev
2018-07-29 14:09 ` Artem Boldarev
2018-07-29 17:33 ` Eli Zaretskii
2018-07-30 6:22 ` martin rudalics
2018-07-30 10:00 ` Artem Boldarev
2018-07-27 16:00 ` Agustin Martin
2018-07-28 0:00 ` Artem Boldarev
2018-07-30 13:20 ` Agustin Martin
2018-07-30 16:29 ` Artem Boldarev
2018-07-30 16:43 ` Agustin Martin
2018-07-30 18:12 ` Artem Boldarev
2018-08-04 10:43 ` Eli Zaretskii
2018-08-07 10:56 ` Artem Boldarev
2018-08-07 15:37 ` Eli Zaretskii
2018-07-28 0:23 ` Artem Boldarev
2018-07-28 7:02 ` Eli Zaretskii
2018-07-29 14:15 ` Artem Boldarev
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83bmassv88.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=32280@debbugs.gnu.org \
--cc=artem.boldarev@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.