From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Michael Albinus Newsgroups: gmane.emacs.devel Subject: Re: Feature change or bug - Emacs server Date: Mon, 13 Jun 2011 19:36:32 +0200 Message-ID: <87vcw98wgv.fsf@gmx.de> References: <4df63f95.a511440a.7545.ffffce92@mx.google.com> <878vt5645m.fsf@lifelogs.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1307986616 6608 80.91.229.12 (13 Jun 2011 17:36:56 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Mon, 13 Jun 2011 17:36:56 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jun 13 19:36:52 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1QWB4F-00011f-1v for ged-emacs-devel@m.gmane.org; Mon, 13 Jun 2011 19:36:51 +0200 Original-Received: from localhost ([::1]:35087 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QWB4E-000501-DF for ged-emacs-devel@m.gmane.org; Mon, 13 Jun 2011 13:36:50 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:50646) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QWB41-0004zw-LK for emacs-devel@gnu.org; Mon, 13 Jun 2011 13:36:38 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QWB40-0003ix-NY for emacs-devel@gnu.org; Mon, 13 Jun 2011 13:36:37 -0400 Original-Received: from mailout-de.gmx.net ([213.165.64.22]:43193) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1QWB40-0003h1-9v for emacs-devel@gnu.org; Mon, 13 Jun 2011 13:36:36 -0400 Original-Received: (qmail invoked by alias); 13 Jun 2011 17:36:33 -0000 Original-Received: from p57BB998E.dip0.t-ipconnect.de (EHLO detlef.gmx.de) [87.187.153.142] by mail.gmx.net (mp056) with SMTP; 13 Jun 2011 19:36:33 +0200 X-Authenticated: #3708877 X-Provags-ID: V01U2FsdGVkX1+SnRpitCeSlTmjBWMWLxN2pOcK1w+e+H6LdOu05/ ElwS4o/k3Bn8Pl In-Reply-To: <878vt5645m.fsf@lifelogs.com> (Ted Zlatanov's message of "Mon, 13 Jun 2011 12:18:45 -0500") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) X-Y-GMX-Trusted: 0 X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 213.165.64.22 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:140425 Archived-At: Ted Zlatanov writes: > For the protocol, I found only > http://live.gnome.org/NetworkManagerConfiguration which is a good > explanation and shows the D-BUS protocol to some degree, but not how to > use the protocol directly. In this case, you might observe the D-Bus system bus via "dbus-monitor --system" and play with your network. In case you have a wireless connection, you will see already the signals about the strength of the connection. > I plan to watch D-BUS anyhow to handle notifications. So it seems that > using D-BUS is inevitable and probably better than relying on > command-line utilities. Is it sufficient? Or are there other pieces? >From my understanding, it is the best approach, at least if you intend to watch for signals. As usual, I'm at your service :-) > Thanks > Ted Best regards, Michael.