[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: async 1.0
Re: async 1.0
Wed, 04 Jul 2012 13:10:47 -0400
MT-NewsWatcher/3.5.2 (PPC Mac OS X)
John Wiegley <address@hidden> wrote:
> >>>>> Michael Albinus <address@hidden> writes:
> > Or you keep the Emacs daemons running in the background, waiting for new
> > tasks. Communication could be via D-Bus (queued services). But I have no
> > idea, how much it would improve reactiveness.
> > And it wouldn't run on all platforms Emacs supports.
> And it introduces state bugs, which would be insane to debug, since presently
> there is no a way to debug the child Emacs. I'm having a hard time even
> getting stack traces from the point of failure (a condition-case handler gives
> you the backtrace for the handler, not the error's origin. This may need new
> functionality in Emacs to pass the trace as part of the error data).
I've long thought Emacs should keep the backtrace along with the
error/condition/exception (whichever you want to call it), like Python
does: the way things are now is fairly painful even for single-process
debugging, in all but the simplest cases. Captured backtraces would
allow the user to manually examine only those errors that they are
actually interested in, and should permit handlers to augment them with
additional information before re-throwing.
- Re: async 1.0, Michael Sperber, 2012/07/01
- Re: async 1.0,
Samuel Bronson <=