From: Artem Boldarev <artem.boldarev@gmail.com>
To: martin rudalics <rudalics@gmx.at>, Eli Zaretskii <eliz@gnu.org>
Cc: 32280@debbugs.gnu.org
Subject: bug#32280: 26.1; FLYSPELL-BUFFER sometimes misbehaves for some input in a large enough buffer
Date: Mon, 30 Jul 2018 13:00:38 +0300 [thread overview]
Message-ID: <02f036ab-dcce-cc43-c0cc-33f0dae1884e@gmail.com> (raw)
In-Reply-To: <5B5EAEB5.4020005@gmx.at>
Hi,
Yes, there is a clear pattern. The wrong behaviour appears only when the
word in Latin, which follows the Cyrillic one, has the length more or
equal to the length of a preceding word.
Here is the sample text:
https://chaoticlab.io/pub/flyspell-bug/sample2/flyspell-sample2.txt
Instructions for the bug reproduction are the same:
https://chaoticlab.io/pub/flyspell-bug/flyspell-bug-reproduction.el
Screenshot without the provided fix:
https://chaoticlab.io/pub/flyspell-bug/sample2/flyspell-bug-sample2.png
Screenshot with the provided fix:
https://chaoticlab.io/pub/flyspell-bug/sample2/flyspell-bug-sample2-fixed.png
It seems logical to me that the provided fix is sufficient for this case
considering what was changed in the problematic function.
Regards,
Artem
> > https://chaoticlab.io/pub/flyspell-bug/flyspell-bug-linux.png
> > https://chaoticlab.io/pub/flyspell-bug/flyspell-bug-windows.png
>
> From these images it seems immediately evident that flyspell wrongly
> marks и, именно, бесконечный and усложняет as misspelled only when a
> non-cyrillic word follows it. However, as paragraph 4 in these
> examples also demonstrates, such condition is not sufficient since
> there the words preceding 'HTML' and 'Lorem Ipsum' are not marked.
>
> Could you try to play around with the seqeuencing of words in that
> example? Maybe a clearer pattern emerges.
>
> Thanks, martin
>
next prev parent reply other threads:[~2018-07-30 10:00 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
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 [this message]
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
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=02f036ab-dcce-cc43-c0cc-33f0dae1884e@gmail.com \
--to=artem.boldarev@gmail.com \
--cc=32280@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=rudalics@gmx.at \
/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).