From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Samuel Bronson Newsgroups: gmane.emacs.devel Subject: Re: async 1.0 Date: Wed, 04 Jul 2012 13:10:47 -0400 Message-ID: References: <87vcij7rvi.fsf@mithlond.arda> <87r4t7sepa.fsf@gmx.de> NNTP-Posting-Host: plane.gmane.org X-Trace: dough.gmane.org 1341421881 15087 80.91.229.3 (4 Jul 2012 17:11:21 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 4 Jul 2012 17:11:21 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jul 04 19:11:21 2012 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1SmT6m-0007js-Mo for ged-emacs-devel@m.gmane.org; Wed, 04 Jul 2012 19:11:20 +0200 Original-Received: from localhost ([::1]:35791 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SmT6l-00078x-Kn for ged-emacs-devel@m.gmane.org; Wed, 04 Jul 2012 13:11:19 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:37573) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SmT6i-00078r-He for emacs-devel@gnu.org; Wed, 04 Jul 2012 13:11:17 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SmT6c-00027W-5F for emacs-devel@gnu.org; Wed, 04 Jul 2012 13:11:16 -0400 Original-Received: from plane.gmane.org ([80.91.229.3]:54622) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SmT6b-00027P-UY for emacs-devel@gnu.org; Wed, 04 Jul 2012 13:11:10 -0400 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1SmT6X-0007H3-Nq for emacs-devel@gnu.org; Wed, 04 Jul 2012 19:11:05 +0200 Original-Received: from 207-172-123-137.c3-0.upd-ubr1.trpr-upd.pa.cable.rcn.com ([207.172.123.137]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 04 Jul 2012 19:11:05 +0200 Original-Received: from naesten by 207-172-123-137.c3-0.upd-ubr1.trpr-upd.pa.cable.rcn.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 04 Jul 2012 19:11:05 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 23 Original-X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: 207-172-123-137.c3-0.upd-ubr1.trpr-upd.pa.cable.rcn.com User-Agent: MT-NewsWatcher/3.5.2 (PPC Mac OS X) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:151420 Archived-At: John Wiegley wrote: > >>>>> Michael Albinus 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.