From: Michael Albinus <michael.albinus@gmx.de>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: emacs-devel@gnu.org
Subject: Re: D-Bus integration into Emacs
Date: Mon, 03 Dec 2007 09:51:08 +0100 [thread overview]
Message-ID: <nqlk8c40w3.fsf@alcatel-lucent.de> (raw)
In-Reply-To: <18259.27327.46121.155608@kahikatea.snap.net.nz> (Nick Roberts's message of "Mon, 3 Dec 2007 15:32:31 +1300")
Nick Roberts <nickrob@snap.net.nz> writes:
> > I've committed the files to the trunk. In order to activate D-Bus
> > integration, one must apply "./configure --with-dbus". It's tested under
> > GNU/Linux only, but there seem to exist D-Bus implementations for Mac OS
> > X and Win32 as well.
>
> If someone has D-Bus on their OS would they want to configure Emacs without
> it? Shouldn't configure just check for this feature and configure Emacs
> to use it if found, as is done with most other features?
I agree, this should be the target. But I've made it configurable for
two reasons:
- The integration touches sensible parts of Emacs, like event
handling. I didn't want to stall everybody due to a possible
error. It works stable in my local environment, but before enabling
it wherever D-Bus exist, there should be kind of feedback from other
people.
- I've tested it only for GNU/Linux (Ubuntu 7.04/7.10, to be precise).
I have no idea how it works on other platforms, like Mac OS X or
Win32. For example, the D-Bus API offers Win32 specific functions
I'll never be able to test. See dbus_connection_get_unix_user vs
dbus_connection_get_windows_user in the API.
So I propose to wait at least some weeks (until the end of this
year?), whether there are serious drawbacks. If not, we could remove
the configuration option "with-dbus".
Best regards, Michael.
next prev parent reply other threads:[~2007-12-03 8:51 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-28 22:19 D-Bus integration into Emacs Michael Albinus
2007-12-02 17:28 ` Michael Albinus
2007-12-02 20:45 ` Eli Zaretskii
2007-12-02 21:47 ` Jason Rumney
2007-12-03 8:37 ` Michael Albinus
2007-12-02 22:40 ` Christian Faulhammer
2007-12-03 2:32 ` Nick Roberts
2007-12-03 7:04 ` Christian Faulhammer
2007-12-03 7:36 ` Nick Roberts
2007-12-03 8:48 ` Christian Faulhammer
2007-12-03 8:59 ` Nick Roberts
2007-12-03 22:04 ` Andreas Schwab
2007-12-04 6:48 ` Christian Faulhammer
2007-12-04 16:55 ` Richard Stallman
2007-12-04 18:18 ` Ulrich Mueller
2007-12-04 20:17 ` Michael Albinus
2007-12-04 20:48 ` Ulrich Mueller
2007-12-04 21:03 ` Michael Albinus
2007-12-04 21:56 ` Magnus Henoch
2007-12-05 6:05 ` Richard Stallman
2007-12-03 8:51 ` Michael Albinus [this message]
2007-12-03 18:42 ` Richard Stallman
2007-12-03 21:11 ` Michael Albinus
2007-12-03 3:17 ` Magnus Henoch
2007-12-03 7:12 ` Jan Djärv
2007-12-03 9:37 ` Andreas Schwab
2007-12-04 7:36 ` Jan Djärv
2007-12-04 10:25 ` Andreas Schwab
2007-12-04 11:30 ` Jan Djärv
2007-12-05 22:51 ` Andreas Schwab
2007-12-06 7:05 ` Jan Djärv
2007-12-06 8:02 ` Glenn Morris
2007-12-06 8:08 ` Thien-Thi Nguyen
2007-12-06 10:01 ` Jan Djärv
2007-12-05 2:56 ` Richard Stallman
2007-12-03 21:41 ` Michael Albinus
2007-12-03 22:05 ` Magnus Henoch
2007-12-04 7:35 ` Jan Djärv
2007-12-03 23:43 ` Johan Bockgård
2007-12-04 21:42 ` Michael Albinus
2007-12-05 10:37 ` Johan Bockgård
-- strict thread matches above, loose matches on Subject: below --
2007-12-05 8:37 Michael Albinus
2007-12-05 14:55 ` Magnus Henoch
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=nqlk8c40w3.fsf@alcatel-lucent.de \
--to=michael.albinus@gmx.de \
--cc=emacs-devel@gnu.org \
--cc=nickrob@snap.net.nz \
/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.