From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 792 invoked by alias); 5 Oct 2010 13:04:30 -0000 Received: (qmail 783 invoked by uid 22791); 5 Oct 2010 13:04:29 -0000 X-SWARE-Spam-Status: No, hits=0.5 required=5.0 tests=AWL,BAYES_50,SPF_NEUTRAL,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from granite1.mail.cornell.edu (HELO authusersmtp.mail.cornell.edu) (128.253.83.141) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 05 Oct 2010 13:04:24 +0000 Received: from [127.0.0.1] (cpe-67-249-196-94.twcny.res.rr.com [67.249.196.94]) (authenticated bits=0) by authusersmtp.mail.cornell.edu (8.14.4/8.12.10) with ESMTP id o95D4LBU002949 for ; Tue, 5 Oct 2010 09:04:21 -0400 (EDT) Message-ID: <4CAB2230.4090500@cornell.edu> Date: Tue, 05 Oct 2010 13:04:00 -0000 From: Ken Brown User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.9) Gecko/20100825 Thunderbird/3.1.3 MIME-Version: 1.0 To: cygwin Subject: Re: emacs-23.2-3 and DBus References: <844od1b8rx.fsf@aol.com> In-Reply-To: <844od1b8rx.fsf@aol.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2010-10/txt/msg00081.txt.bz2 On 10/4/2010 11:47 PM, nyc4bos@aol.com wrote: > Thank you for your work on incorporating Emacs and DBus! > > Can you tell me how you are testing it? > > I tried to use notifiations.el (from the Emacs 24 trunk). > > After loading it, Emacs appears to freeze and I see that > the emacs and winlogin.exe processes consume almost all of > the CPU. > > After about 30 to 45 minutes, I pressed `C-g' and saw the > message "Back to top level.". > > However, Emacs is still frozen and the only thing I could > do is to kill emacs from outside of emacs. Please send Cygwin questions to the Cygwin mailing list, not to individual maintainers. I know virtually nothing about D-Bus. To test it, I simply followed the instructions given by Michael Albinus in the thread http://cygwin.com/ml/cygwin/2010-08/threads.html#00330 . Here's a brief summary: 1. Start the messagebus service. 2. Start a dbus session (eval `dbus-launch --auto-syntax`) in a shell. 3. echo $DBUS_SESSION_BUS_ADDRESS . 4. In a different shell, set (and export) $DBUS_SESSION_BUS_ADDRESS to this value, and run dbus-monitor --session . 5. Start Emacs in the first shell, and load the dbus library. You should see output from dbus-monitor in the other shell, showing that an application has started. It will also tell you the name of that application, like ":1.1". 6. In Emacs, evaluate (dbus-get-unique-name :session) . You should get the same name. 7. Register for signals sent by the D-Bus: (defun my-dbus-signal-handler (&rest args) (message "Signal from bus %s received: %s" (dbus-event-bus-name last-input-event) args)) (dbus-register-signal :system dbus-service-dbus dbus-path-dbus dbus-interface-dbus "NameOwnerChanged" 'my-dbus-signal-handler) (dbus-register-signal :session dbus-service-dbus dbus-path-dbus dbus-interface-dbus "NameOwnerChanged" 'my-dbus-signal-handler) 8. Now you could open any other D-Bus application, and you should be notified in Emacs (in the echo area and the *Messages* buffer). For example, you could try dbus-monitor --session , started in the same shell where you started Emacs. I'm afraid that's all I know. Unless you think there is a Cygwin-specific problem, further questions should probably be directed to one of the Emacs lists, where you will find people who are knowledgeable about D-Bus integration in Emacs. BTW, there has been quite a bit of development of this integration since the release of Emacs 23.2. Some improvements will appear in Emacs 23.3, and some won't appear until 24.1. So if you're trying to use a library from the Emacs 24 trunk, it's possible that it's simply not compatible with Emacs 23. Ken -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple