From: Agustin Martin <agustin6martin@gmail.com>
To: 32280@debbugs.gnu.org, Artem Boldarev <artem.boldarev@gmail.com>
Subject: bug#32280: 26.1; FLYSPELL-BUFFER sometimes misbehaves for some input in a large enough buffer
Date: Mon, 30 Jul 2018 15:20:33 +0200 [thread overview]
Message-ID: <20180730132033.GA1182@agmartin.aq.upm.es> (raw)
In-Reply-To: <f7ef3ea8-0b94-975c-6ce7-bc804a71018e@gmail.com>
On Sat, Jul 28, 2018 at 03:00:40AM +0300, Artem Boldarev wrote:
> Hello Agustin,
>
> Thanks for your suggestion!
>
> Unfortunately, it does not work on my system with 'emacs -Q'. So, somehow I
> need to manually configure my dictionaries anyway. I will consider replacing
> 'ispell-dictionary-alist'with 'ispell-local-dictionary-alist' in my
> configuration. Thank you for pointing out.
Hi,
I am using your example file with emacs -Q (Emacs 25) and had no problems,
flyspell-buffer works as expected after setting ispell-program-name to
hunspell and set ru_RU as dict (hunspell 1.6.2 here).
Local Ispell dictionary set to ru_RU
Starting new Ispell process hunspell with ru_RU dictionary...
Checking region...
Spell Checking...100% [laborum]
Spell Checking completed.
The auto-detected values for hunspell ru_RU are
(ru_RU [[:alpha:]] [^[:alpha:]] t (-d ru_RU) nil utf-8)
Wonder why otherchars is not shown.
> The codepage I specified in the configuration, as it seems, is not the
> problem as spell checking works fine *most* of the time. I could spellcheck
> large amounts of text without any issues. It seems that hunspell always uses
> utf-8 internally, but I am not sure: I will try to investigate this.
Seems I was wrong, it is a long time since I digged there.
¿What happens if you use "[[:alpha:]]" and "[^[:alpha:]]" instead if the
explicit character strings "[АБВГДЕЁЖЗИЙКЛМНОПРСТУФХЦЧШЩЬЫЪЭЮЯабвгдеёжзийклмнопрстуфхцчшщьыъэюя]"
and "[^АБВГДЕЁЖЗИЙКЛМНОПРСТУФХЦЧШЩЬЫЪЭЮЯабвгдеёжзийклмнопрстуфхцчшщьыъэюя]"?
Regards,
--
Agustin
next prev parent reply other threads:[~2018-07-30 13:20 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
2018-07-27 16:00 ` Agustin Martin
2018-07-28 0:00 ` Artem Boldarev
2018-07-30 13:20 ` Agustin Martin [this message]
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=20180730132033.GA1182@agmartin.aq.upm.es \
--to=agustin6martin@gmail.com \
--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 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).