From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: emacs-devel@gnu.org
Subject: Re: Proposal for a new mechanism for delayed stuff
Date: Thu, 03 Jan 2013 20:56:31 -0500 [thread overview]
Message-ID: <jwv623diuet.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <m31ue1j0xy.fsf@stories.gnus.org> (Lars Magne Ingebrigtsen's message of "Fri, 04 Jan 2013 00:34:17 +0100")
>>> Sure, that would also handle the "tell the user what's going on" use
>>> case, and we could have a convenience macro `with-current-state-message'
>>> that would simply be an `unwind-protect' to clear out the state message.
>> Yes, the advantage is that the message can be displayed even if we're in
>> the middle of uninterruptible Elisp code.
> Well, presumably if we can display `current-state-message' in
> uninterruptible Elisp code, we could also do the `with-timeout-forms'
> things in the uninterruptible Elisp code?
No, because that would mean running arbitrary code in the middle of
"uninterruptible Elisp code", which is contrary to the idea of
"uninterruptible".
> Anyway, if `current-state-message' is easy to implement, I'm all for
> getting that. :-)
I don't know if it is.
Stefan
prev parent reply other threads:[~2013-01-04 1:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-25 13:20 Proposal for a new mechanism for delayed stuff Lars Ingebrigtsen
2012-12-25 13:52 ` Xue Fuqiao
2012-12-25 19:57 ` Karl Fogel
2012-12-26 14:08 ` Ted Zlatanov
2012-12-27 4:08 ` Stephen J. Turnbull
2012-12-27 10:49 ` Achim Gratz
2012-12-27 14:43 ` Stephen J. Turnbull
2012-12-27 9:40 ` Vitalie Spinu
2012-12-27 14:01 ` Lars Ingebrigtsen
2012-12-29 6:30 ` Stefan Monnier
2012-12-31 14:09 ` Lars Magne Ingebrigtsen
2013-01-03 16:47 ` Stefan Monnier
2013-01-03 23:34 ` Lars Magne Ingebrigtsen
2013-01-04 1:56 ` Stefan Monnier [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
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=jwv623diuet.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.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 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).