emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Issue connecting Emacs --daemon to D-BUS


From: andres . ramirez
Subject: Re: Issue connecting Emacs --daemon to D-BUS
Date: Tue, 02 Oct 2012 00:38:05 -0500
User-agent: SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (Goj┼Ź) APEL/10.8 Emacs/24.2 (x86_64-unknown-linux-gnu) MULE/6.0 (HANACHIRUSATO)

Hi Joakim.

From a Discussion with Michael Albinus.

This is what works for me. Using the emacs trunk:

- You start the daemon as usual via crontab:

  @reboot /usr/local/src/emacs/src/emacs --quick --eval \(progn\ \(setq\ 
server-name\ \"test\"\)\ \) --daemon

- In your emacsclient call, you hand over $DBUS_SESSION_BUS_ADDRESS via
  the variable `my-dbus-address':

  emacsclient -s test -c -e \(setq\ my-dbus-address\ 
\"$DBUS_SESSION_BUS_ADDRESS\"\)

  Instead of expanding $DBUS_SESSION_BUS_ADDRESS you could use any
  address string, once you know it.

- In your Emacs daemon, you can now apply the following code:

  (progn
    (require 'notifications)
    (dbus-init-bus my-dbus-address)
    (notifications-notify
     :bus my-dbus-address
     :title "nick"
     :body "message"
     :app-icon 
"/usr/share/notify-osd/icons/gnome/scalable/status/notification-message-im.svg"
     :urgency 'low))

The crucial point is calling `dbus-init-bus' and using the bus address
as argument of `notifications-notify'. `dbus-init-bus' must be called
only once for a new address, but it doesn't hurt when you call it
always. Btw, there was a subtle bug in `dbus-init-bus', which took me so
long to test ...

Now your notifications shall be visible, wherever you call emacsclient
from. Even if you stop your session, and restart it, it shall work,
because the new D-Bus session bus will be found.

At Thu, 27 Sep 2012 11:42:13 +0200,
address@hidden wrote:
> 
> This will be a rather vague problem description, sorry.
> 
> I'm trying to start using Emacs in its daemonic form:
> emacs --daemon
> 
> The idea is that since the Gnome 3 gnome-shell sometimes crashes several 
> times a
> day for me, my emacs will survive and I can simply reconnect with
> emacsclient once gnome-shell is up again.
> 
> Since I want my emacs to start as a service daemon when the machine
> boots, there is no dbus or gnome session to connect to yet. I want to
> attach to dbus and gnome once the gui session is started.
> 
> 
> 
> for the gnome keyring I can do this:
> m-x setenv SSH_AUTH_SOCK RET /run/user/joakim/keyring-hzCXZo/ssh RET
> 
> where the value is fetched from a shell started within the login
> session. I can thus unlock the keyring in gnome and use it in emacs.
> 
> I expect to be able to do the same for dbus, but it doesnt quite work:
> 
> m-x setevn DBUS_SESSION_BUS_ADDRESS RET
> unix:abstract=/tmp/dbus-XpKHIj1IpU,guid=5a7b419d5e50e78fe35e6ccf0005787a
> RET
> 
> I still get:
> 
> ELISP> (dbus-init-bus :session)
> *** Eval error ***  D-Bus error: "No connection to bus", :session
> 
> And here somewhere is my actuall issue: "No connection to bus" can be
> returned in several places in dbusbind.c, so I cant really debug which
> of the checks are triggered. 
> 
> 
> (dbus-init-bus :system) seems to work and return 2.
> -- 
> Joakim Verona
> 
> 



reply via email to

[Prev in Thread] Current Thread [Next in Thread]