From: "Davis Herring" <herring@lanl.gov>
To: "Thien-Thi Nguyen" <ttn@gnuvola.org>
Cc: Michael Albinus <michael.albinus@gmx.de>,
rms@gnu.org, emacs-devel@gnu.org
Subject: Re: callback functions in Emacs
Date: Wed, 5 Sep 2007 07:30:11 -0700 (PDT) [thread overview]
Message-ID: <60290.128.165.123.18.1189002611.squirrel@webmail.lanl.gov> (raw)
In-Reply-To: <873axtz9ng.fsf@gnuvola.org>
> how about extending emacsclient to communicate d-bus messages?
> that should be able to handle all three of these cases, and
> furthermore handle disambiguation of multiple emacs instances.
Perhaps I misunderstand D-Bus (having only glanced at its front page), but
I believe that messages can only be delivered to processes (that already
exist). We'd have to have some sort of emacsclientserver (perhaps within
Emacs) that listened for them and translated them into emacsclient
invocations. Of course, if such a server is in Emacs, it prevents having
another program to customize, but then it might as well do what the OP
suggests and handle the messages itself.
Davis
--
This product is sold by volume, not by mass. If it appears too dense or
too sparse, it is because mass-energy conversion has occurred during
shipping.
next prev parent reply other threads:[~2007-09-05 14:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-04 20:27 callback functions in Emacs Michael Albinus
2007-09-04 21:21 ` David Kastrup
2007-09-04 22:32 ` Davis Herring
2007-09-05 1:15 ` Stefan Monnier
2007-09-05 6:16 ` Richard Stallman
2007-09-05 8:43 ` Michael Albinus
2007-09-05 10:01 ` Miles Bader
2007-09-05 15:31 ` Michael Albinus
2007-09-05 10:30 ` Thien-Thi Nguyen
2007-09-05 10:48 ` Michael Albinus
2007-09-05 14:30 ` Davis Herring [this message]
2007-09-05 15:18 ` Michael Albinus
2007-09-05 16:09 ` Stefan Monnier
2007-09-05 16:40 ` Thien-Thi Nguyen
2007-09-06 6:12 ` dhruva
2007-09-05 15:34 ` Leo
2007-09-06 4:59 ` Richard Stallman
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=60290.128.165.123.18.1189002611.squirrel@webmail.lanl.gov \
--to=herring@lanl.gov \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
--cc=rms@gnu.org \
--cc=ttn@gnuvola.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 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.