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: Wrong type error in dbus method Date: Fri, 09 Jul 2010 21:47:34 +0200 Message-ID: <87zky0o2sp.fsf@gmx.de> References: <4c2d4db9.df0ae50a.241a.0135@mx.google.com> <87mxuap83w.fsf@ambire.localdomain> <87630x9c11.fsf@gmx.de> <878w5qpaka.fsf@ambire.localdomain> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: dough.gmane.org 1278704869 24591 80.91.229.12 (9 Jul 2010 19:47:49 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Fri, 9 Jul 2010 19:47:49 +0000 (UTC) Cc: Patrick Michael Niedzielski , emacs-devel@gnu.org To: Thien-Thi Nguyen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jul 09 21:47:47 2010 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1OXJY2-0006Np-P9 for ged-emacs-devel@m.gmane.org; Fri, 09 Jul 2010 21:47:47 +0200 Original-Received: from localhost ([127.0.0.1]:46566 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OXJY2-00023y-7d for ged-emacs-devel@m.gmane.org; Fri, 09 Jul 2010 15:47:46 -0400 Original-Received: from [140.186.70.92] (port=48314 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OXJXx-00023n-CL for emacs-devel@gnu.org; Fri, 09 Jul 2010 15:47:42 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OXJXw-0003m8-6B for emacs-devel@gnu.org; Fri, 09 Jul 2010 15:47:41 -0400 Original-Received: from mail.gmx.net ([213.165.64.20]:45938) by eggs.gnu.org with smtp (Exim 4.69) (envelope-from ) id 1OXJXv-0003ln-Ri for emacs-devel@gnu.org; Fri, 09 Jul 2010 15:47:40 -0400 Original-Received: (qmail invoked by alias); 09 Jul 2010 19:47:37 -0000 Original-Received: from p4FC18F73.dip0.t-ipconnect.de (EHLO detlef.gmx.de) [79.193.143.115] by mail.gmx.net (mp064) with SMTP; 09 Jul 2010 21:47:37 +0200 X-Authenticated: #3708877 X-Provags-ID: V01U2FsdGVkX1/jKwxITMnjv0a1jYoOsqVl5MU8mbGAvkUoGh60iq PNhW5OQVTmzWMX In-Reply-To: <878w5qpaka.fsf@ambire.localdomain> (Thien-Thi Nguyen's message of "Mon, 05 Jul 2010 11:00:53 +0200") 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-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:126964 Archived-At: Thien-Thi Nguyen writes: > I typed =E2=80=98i=E2=80=99 and Emacs beeped: "No index". That's a big h= ole. > [If i were maintaining Emacs, i would add "all manuals have an > index" as a strong requirement in admin/FOR-RELEASE (Manuals).] Added. > Re this particular problem (incorrect list construction), perhaps > where it reads: > > All other arguments args are passed to METHOD as arguments. They > are converted into D-Bus types as described in *note Type > Conversion::. > > you could link to the Emacs Lisp manual, node "(elisp) Building Lists". I've refrained from adding this. The concrete error was not related to special dbus.el handling; pointing to list construction could be added to any package specific manual otherwise ... > I see this blurb is repeated in both Synchronous Methods and Asynchronous > Methods, so another idea is to add to Overview a small section "Audience", > with appropriate hints/links on Emacs Lisp programming, message bus fu, > network etiquette, etc. The primary message there would be "to get the > best out of this manual (& the API it describes & the peers with whom you > will likely be communicating), move your mind here, first". Of course, > if you are a mechanism/policy separation purist, this might chafe a bit. This might be worth to add. But I still need some thinking about, because it could tend to explain DBus itself, which shouldn't be done in dbus.texi. > thi Best regards, Michael.