From: Michael Albinus <michael.albinus@gmx.de>
To: pmlists@free.fr (Peter Münster)
Cc: help-gnu-emacs@gnu.org
Subject: Re: dbus: "(setenv ...)" not the same as "export ...=..."
Date: Mon, 07 Nov 2011 11:07:30 +0100 [thread overview]
Message-ID: <87lirsfdp9.fsf@gmx.de> (raw)
In-Reply-To: <87mxcizfdw.fsf@micropit.couberia.bzh> ("Peter \=\?utf-8\?Q\?M\?\= \=\?utf-8\?Q\?\=C3\=BCnster\=22's\?\= message of "Sun, 30 Oct 2011 16:08:11 +0100")
pmlists@free.fr (Peter Münster) writes:
> I don't want to start it from emacs. It has already been started from
> somewhere at the start of the X-session. The "address=autolaunch"
> permits emacs to find the dbus-daemon.
>
> From the dbus-launch man page:
> "If DBUS_SESSION_BUS_ADDRESS is not set for a process that tries to
> use D-Bus, by default the process will attempt to invoke dbus-launch
> with the --autolaunch option to start up a new session bus or find
> the existing bus address on the X display or in a file in
> ~/.dbus/session-bus/"
>
> It seems, that emacs does this only, if DBUS_SESSION_BUS_ADDRESS is set
> to "autolaunch:", but not if it is unset. And (setenv ...) does not
> work, it must be set from outside emacs.
Emacs' dbusbind.c does not parse $DBUS_SESSION_BUS_ADDRESS, it uses
vanilla libdbus from the reference implementation. Therefore, its
behaviour seems to be correct.
For the behaviour of `setenv' see the other answer. It modifies
`process-environment', which is not involved 'cause there is no new
process started when opening a D-Bus connection.
Best regards, Michael.
next prev parent reply other threads:[~2011-11-07 10:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-29 23:44 dbus: "(setenv ...)" not the same as "export ...=..." Peter Münster
2011-10-30 8:51 ` Michael Albinus
2011-10-30 15:08 ` Peter Münster
2011-11-07 10:07 ` Michael Albinus [this message]
2011-11-02 4:56 ` Kevin Rodgers
2011-11-02 21:54 ` Peter Münster
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lirsfdp9.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=help-gnu-emacs@gnu.org \
--cc=pmlists@free.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.