From: Spencer Baugh <sbaugh@janestreet.com>
To: emacs-devel@gnu.org
Subject: Re: unwind-protect within while-no-input
Date: Wed, 08 May 2024 15:28:38 -0400 [thread overview]
Message-ID: <ier34qsqf15.fsf@janestreet.com> (raw)
In-Reply-To: 86r0ec87d5.fsf@gnu.org
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Spencer Baugh <sbaugh@janestreet.com>
>> Date: Wed, 08 May 2024 11:14:05 -0400
>>
>> If I have a function:
>>
>> (defun my-function ()
>> ...do something...)
>>
>> which might be invoked by some other package that I don't control like this:
>>
>> (defun some-other-package ()
>> (while-no-input
>> ...
>> (my-function)
>> ...))
>>
>> How does my-function run the unwind-forms when it is interrupted by
>> while-no-input?
>
> How can a function cause its caller to do anything at all? It can't.
> If the caller wants to make sure some unwind-forms will always run
> after my-function either returns locally or exits non-locally, the
> caller needs to arrange for that.
I don't want to run the unwind forms "after" my-function returns or
exits. I want them to run wherever they are inside my-function, just
like a normal unwind-protect.
Let me try to explain again what I want: I want a completely normal
unwind-protect, exactly how unwind-protect works normally:
(unwind-protect BODYFORM UNWINDFORMS...)
Do BODYFORM, protecting with UNWINDFORMS.
If BODYFORM completes normally, its value is returned
after executing the UNWINDFORMS.
If BODYFORM exits nonlocally, the UNWINDFORMS are executed anyway.
Except that I want the UNWINDFORMS to not be interrupted by a
*surrounding* while-no-input or quit or any other kind of nonlocal exit.
Is there any way to do that? ("Move the while-no-input inside the
unwind-protect" is not an answer, because then it's not a *surrounding*
while-no-input anymore)
next prev parent reply other threads:[~2024-05-08 19:28 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 12:45 unwind-protect within while-no-input Spencer Baugh
2024-05-07 18:05 ` Spencer Baugh
2024-05-07 18:49 ` Eli Zaretskii
2024-05-07 19:43 ` Spencer Baugh
2024-05-08 3:59 ` Po Lu
2024-05-08 11:42 ` Michael Heerdegen via Emacs development discussions.
2024-05-08 11:47 ` Michael Heerdegen via Emacs development discussions.
2024-05-08 13:44 ` Spencer Baugh
2024-05-08 16:13 ` Michael Heerdegen via Emacs development discussions.
2024-05-08 17:18 ` Spencer Baugh
2024-05-08 20:43 ` Michael Heerdegen via Emacs development discussions.
2024-05-09 12:57 ` Spencer Baugh
2024-05-09 14:13 ` Michael Heerdegen via Emacs development discussions.
2024-05-08 12:12 ` Eli Zaretskii
2024-05-08 12:36 ` Michael Heerdegen via Emacs development discussions.
2024-05-08 11:52 ` Eli Zaretskii
2024-05-08 13:57 ` Spencer Baugh
2024-05-08 14:18 ` Eli Zaretskii
2024-05-08 14:38 ` Spencer Baugh
2024-05-08 15:06 ` Eli Zaretskii
2024-05-08 15:14 ` Spencer Baugh
2024-05-08 18:51 ` Eli Zaretskii
2024-05-08 19:28 ` Spencer Baugh [this message]
2024-05-09 5:46 ` Eli Zaretskii
2024-05-09 13:07 ` Spencer Baugh
2024-05-09 17:41 ` Dmitry Gutov
2024-05-11 9:48 ` Eli Zaretskii
2024-05-11 10:37 ` Eshel Yaron
2024-05-11 10:42 ` Zhengyi Fu
2024-05-11 21:45 ` Dmitry Gutov
2024-05-11 22:08 ` Daniel Mendler via Emacs development discussions.
2024-05-12 1:59 ` Dmitry Gutov
2024-05-12 8:50 ` Daniel Mendler via Emacs development discussions.
2024-05-12 11:49 ` Dmitry Gutov
2024-05-14 21:30 ` Dmitry Gutov
2024-05-26 2:49 ` Stefan Monnier via Emacs development discussions.
2024-05-26 15:36 ` Dmitry Gutov
2024-05-26 18:00 ` Stefan Monnier
2024-05-26 22:56 ` Dmitry Gutov
2024-05-29 0:39 ` Stefan Monnier
2024-05-29 1:17 ` Dmitry Gutov
2024-05-08 20:34 ` Michael Heerdegen via Emacs development discussions.
2024-05-08 16:17 ` Michael Heerdegen via Emacs development discussions.
2024-05-26 2:47 ` Stefan Monnier via Emacs development discussions.
2024-05-26 4:36 ` Stefan Monnier
2024-05-26 4:55 ` Eli Zaretskii
2024-05-26 18:12 ` Stefan Monnier
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=ier34qsqf15.fsf@janestreet.com \
--to=sbaugh@janestreet.com \
--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.