all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ilya Zakharevich <nospam-abuse@ilyaz.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: interacting during (sit-for 0). Was: [PATCH] 5x speedup of flyspell-buffer
Date: Fri, 14 Apr 2023 19:01:20 -0700	[thread overview]
Message-ID: <ZDoFcG+s6V36gZJ/@math.berkeley.edu> (raw)
In-Reply-To: <ZDoDI438oEVYTFnV@math.berkeley.edu>

On Fri, Apr 14, 2023 at 06:51:31PM -0700, Ilya Zakharevich wrote:
> Suppose that a variable `recursive-edit-exit-on-idle' is supported by
> the even loop.  Would then the following code implement
>   (sit-for-0-interactively 'READ-ONLY)
> correctly?
> 
> 	(if (or unread-command-events unread-input-method-events unread-post-input-method-events)
> ;;;	  (with-current-buffer flyspell-large-region-buffer
> 	    (let ((buffer-read-only t) (inhibit-read-only nil)
> 		  (recursive-edit-exit-on-idle t))
> 	      (condition-case nil
> 		  (recursive-edit)
> 		(error nil))));;;)

Thinking on this more: 'quit should be propagated (since the user
should not know about an extra level of recursion).

Moreover, the implementation of `recursive-edit-exit-on-idle' should
disallow entering EXTRA LEVELS of recursive edit when this variable is set.


> Thanks,
> Ilya



      reply	other threads:[~2023-04-15  2:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-12 13:50 [PATCH] 5x speedup of flyspell-buffer Ilya Zakharevich
2023-04-13  6:54 ` Eli Zaretskii
2023-04-13 10:23   ` Ilya Zakharevich
2023-04-13 10:32     ` Eli Zaretskii
2023-04-13 20:29       ` Ilya Zakharevich
2023-04-14  5:47         ` Eli Zaretskii
2023-04-14  6:39           ` Dr. Arne Babenhauserheide
2023-04-14  6:54             ` Eli Zaretskii
2023-04-15  1:51     ` interacting during (sit-for 0). Was: " Ilya Zakharevich
2023-04-15  2:01       ` Ilya Zakharevich [this message]

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=ZDoFcG+s6V36gZJ/@math.berkeley.edu \
    --to=nospam-abuse@ilyaz.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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.