From: Michael Albinus <michael.albinus@gmx.de>
To: mah@everybody.org (Mark A. Hershberger)
Cc: emacs-devel@gnu.org
Subject: Re: dbus library functions
Date: Mon, 01 Dec 2008 06:40:48 +0100 [thread overview]
Message-ID: <87skp8mp0f.fsf@gmx.de> (raw)
In-Reply-To: <8763m6xgvi.fsf@everybody.org> (Mark A. Hershberger's message of "Sat, 29 Nov 2008 18:16:33 -0500")
mah@everybody.org (Mark A. Hershberger) writes:
> I'm interested in making a library of common dbus services available in
> Emacs.
>
> Three logical services would be Notify, On Screen Display, and Avahi.
> Perhaps some of the power management information available via DBus
> would be useful to battery.el, as well.
>
> So, two questions:
>
> 1. Would building Emacs Lisp functions to encapsulate some of the DBus
> information be useful to include in the core?
There are already some of them: xesam.el, zeroconf.el.
> 2. Would it be better to create separate libraries (e.g. notify.el,
> osd.el, avahi.el) or a single one (e.g. freedesktop-dbus.el) for
> these functions?
I believe, separate libraries are the better approach. And zeroconf.el
*IS* your planned avahi.el.
I was thinking about writing something like notify.el, but other
projects had priority. osd.el might be useful, too.
Anyway, we have feature freeze, so I assume you must postpone your
proposals until after-the-release. I have also some libraries in the
queue, which wait for that (xesam-debbugs.el - an interface to the Emacs
bug tracking system; collabora.el - support for collaborative editing;
tramp-gvs.el - using Tramp via the gvfs daemon).
Btw, it would be great, if you could comment the existing D-Bus based
packages, especially zeroconf.el. I didn't receive so much feedback
until now.
> Thanks,
>
> Mark.
Best regards, Michael.
next prev parent reply other threads:[~2008-12-01 5:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-29 23:16 dbus library functions Mark A. Hershberger
2008-11-30 5:37 ` Stefan Monnier
2008-12-01 5:40 ` Michael Albinus [this message]
2008-12-01 15:05 ` Mark A. Hershberger
2008-12-01 15:22 ` Michael Albinus
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87skp8mp0f.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=emacs-devel@gnu.org \
--cc=mah@everybody.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).