From: martin rudalics <rudalics@gmx.at>
To: Artem Boldarev <artem.boldarev@gmail.com>, 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 08:22:45 +0200 [thread overview]
Message-ID: <5B5EAEB5.4020005@gmx.at> (raw)
In-Reply-To: <a6727881-fe39-cf2a-fcf7-20722e9960e8@gmail.com>
> 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 6:22 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 [this message]
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=5B5EAEB5.4020005@gmx.at \
--to=rudalics@gmx.at \
--cc=32280@debbugs.gnu.org \
--cc=artem.boldarev@gmail.com \
--cc=eliz@gnu.org \
/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.