Re: Proposal for a new mechanism for delayed stuff

[Lars Magne Ingebrigtsen]

Stefan Monnier <address@hidden> writes:

>> 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?

Or is that too difficult?

Anyway, if `current-state-message' is easy to implement, I'm all for
getting that.   :-)

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/