From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Michael Albinus Newsgroups: gmane.emacs.devel Subject: Re: Why doesn't dbus-handle-event catch all errors? Date: Fri, 21 Feb 2014 08:22:45 +0100 Message-ID: <87sirdx73u.fsf@gmx.de> References: <5306D806.7050909@dancol.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1392967383 6708 80.91.229.3 (21 Feb 2014 07:23:03 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 21 Feb 2014 07:23:03 +0000 (UTC) Cc: Emacs developers To: Daniel Colascione Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Feb 21 08:23:09 2014 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 1WGkRu-0007U4-6W for ged-emacs-devel@m.gmane.org; Fri, 21 Feb 2014 08:23:06 +0100 Original-Received: from localhost ([::1]:42599 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WGkRt-0005zN-OU for ged-emacs-devel@m.gmane.org; Fri, 21 Feb 2014 02:23:05 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:33772) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WGkRl-0005yU-GS for emacs-devel@gnu.org; Fri, 21 Feb 2014 02:23:03 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WGkRf-0001Lu-6C for emacs-devel@gnu.org; Fri, 21 Feb 2014 02:22:57 -0500 Original-Received: from mout.gmx.net ([212.227.17.22]:56310) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WGkRe-0001LY-TD for emacs-devel@gnu.org; Fri, 21 Feb 2014 02:22:51 -0500 Original-Received: from detlef.gmx.de ([93.209.84.200]) by mail.gmx.com (mrgmx101) with ESMTPS (Nemesis) id 0LzGV3-1XKlHD34Of-014Uur for ; Fri, 21 Feb 2014 08:22:47 +0100 In-Reply-To: <5306D806.7050909@dancol.org> (Daniel Colascione's message of "Thu, 20 Feb 2014 20:37:26 -0800") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) X-Provags-ID: V03:K0:CNRvWvG+KqHNX4+HXuqWThCwfRm1mwiNPOEGWDlqHUj6F9F2a4r NiB4cXinHzydnGAl/egZUrirlbiZhBTaV5EaCO2bfD6wLHHK3U0319WjGyxq4/d04Z/9QK6 cnTc9qdTygMPoLVIa0BqivOzCZv0V/0T5/8HINXoe5zd6IoTKwg2f8tctBevm1YoO4M2xQe eXnoxJrgGepKpdhK//1YQ== X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4.x-2.6.x [generic] X-Received-From: 212.227.17.22 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:169801 Archived-At: Daniel Colascione writes: > dbus-handle-event uses a condition-case that catches dbus-error, but > errors in general. Why don't we send all lisp errors from handler > functions back to callers as dbus errors? Because they aren't dbus errors. If your handler has some stupid code like `(car 42)', the resulting lisp error `(wrong-type-argument listp 42)' shouldn't be shown as *dbus* error. You're free to write a handler which returns any error as dbus error, if your program logic requires this. Best regards, Michael.