all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Artem Boldarev <artem.boldarev@gmail.com>
Cc: 32280-done@debbugs.gnu.org, agustin6martin@gmail.com
Subject: bug#32280: 26.1; FLYSPELL-BUFFER sometimes misbehaves for some input in a large enough buffer
Date: Tue, 07 Aug 2018 18:37:29 +0300	[thread overview]
Message-ID: <837el2qjba.fsf@gnu.org> (raw)
In-Reply-To: <678a1017-47c5-f74f-3b1b-2a15485b6a2d@gmail.com> (message from Artem Boldarev on Tue, 7 Aug 2018 13:56:58 +0300)

> Cc: agustin6martin@gmail.com, 32280@debbugs.gnu.org
> From: Artem Boldarev <artem.boldarev@gmail.com>
> Date: Tue, 7 Aug 2018 13:56:58 +0300
> 
> Thanks, Eli! I have tried the proposed patch, and it seems to solve the 
> problem.
> 
> Thanks to everyone who have helped to track down the problem.
> 
> By the way, are there any chances to see these changes incorporated into 
> Emacs 26.2?

Thanks for testing, I pushed the fix to the emacs-26 branch, and I'm
closing the bug.





  reply	other threads:[~2018-08-07 15:37 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
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 [this message]
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=837el2qjba.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=32280-done@debbugs.gnu.org \
    --cc=agustin6martin@gmail.com \
    --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.