From e74335088374a8b38d3f4f763030eb648a01f801 Mon Sep 17 00:00:00 2001 From: Michael Albinus Date: Mon, 26 Jan 2009 20:23:49 +0000 Subject: [PATCH] * dbus.texi (Errors and Events): New variable dbus-event-error-hooks. --- doc/misc/ChangeLog | 4 ++++ doc/misc/dbus.texi | 17 ++++++++++++++++- 2 files changed, 20 insertions(+), 1 deletion(-) diff --git a/doc/misc/ChangeLog b/doc/misc/ChangeLog index 4296cb4e61..352573f9a6 100644 --- a/doc/misc/ChangeLog +++ b/doc/misc/ChangeLog @@ -1,3 +1,7 @@ +2009-01-26 Michael Albinus + + * dbus.texi (Errors and Events): New variable dbus-event-error-hooks. + 2009-01-26 Glenn Morris * org.texi: Fix typos. diff --git a/doc/misc/dbus.texi b/doc/misc/dbus.texi index 1702c8b434..a6d042a850 100644 --- a/doc/misc/dbus.texi +++ b/doc/misc/dbus.texi @@ -1535,7 +1535,22 @@ from. It is either a signal name or a method name. D-Bus errors are not propagated during event handling, because it is usually not desired. D-Bus errors in events can be made visible by -setting the variable @code{dbus-debug} to @code{t}. +setting the variable @code{dbus-debug} to @code{t}. They can also be +handled by a hook function. + +@defvar dbus-event-error-hooks +This hook variable keeps a list of functions, which are called when a +D-Bus error happens in the event handler. Every function must accept +one argument, the error variable catched in @code{condition-case} by +@code{dbus-error}. Example: + +@lisp +(defun my-dbus-event-error-handler (err) + (message "my-dbus-event-error-handler: %S" (cadr err))) + +(add-hook 'dbus-event-error-hooks 'my-dbus-event-error-handler) +@end lisp +@end defvar @node GNU Free Documentation License -- 2.39.2