From: Richard Stallman <rms@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: emacs-devel@gnu.org
Subject: Re: callback functions in Emacs
Date: Wed, 05 Sep 2007 02:16:29 -0400 [thread overview]
Message-ID: <E1ISoBh-0006Dh-NH@fencepost.gnu.org> (raw)
In-Reply-To: <87642qmb0g.fsf@gmx.de> (message from Michael Albinus on Tue, 04 Sep 2007 22:27:43 +0200)
I'm playing a little bit with integration of D-Bus(*) into Emacs.
It isn't feasible for me to browse a web site--what is D-Bus? Why do
we want to control it from Emacs, and do it by adding C code?
One of the basic concepts od D-Bus is, that one could register a
callback function which is applied when there bis a signal on the bus
one has registered for.
By "signal" do you mean the C-level signals that are handled
by `sigaction'?
But that looks ugly to me. Isn't there another, more simple way to
evaluate Lisp code from inside a callback function?
What do you mean by "a callback function"? That is not an Emacs
concept, so it doesn't specify the most relevant facts. What exactly
is going to call this function, when?
If you're talking about C-level signal handlers, the usual way for
them to run Lisp code is by queuing input events.
next prev parent reply other threads:[~2007-09-05 6:16 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 [this message]
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
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
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=E1ISoBh-0006Dh-NH@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
/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).