[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Wrong type error in dbus method

From: Patrick Michael Niedzielski
Subject: Re: Wrong type error in dbus method
Date: Mon, 05 Jul 2010 15:45:45 +0000


On Mon, 2010-07-05 at 11:00 +0200, Thien-Thi Nguyen wrote: 
> () Michael Albinus <address@hidden>
> () Sat, 03 Jul 2010 10:59:06 +0200
>    Which information do you miss in the dbus info manual?
> I typed ā€˜iā€™ and Emacs beeped: "No index".  That's a big hole.
> [If i were maintaining Emacs, i would add "all manuals have an
> index" as a strong requirement in admin/FOR-RELEASE (Manuals).]

I cannot confirm this particular problem, because I use Debian, which
doesn't give me manuals by default.  I found the dbus documntation only
by going to the CVS repo and downloading the texinfo file.

> 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 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.

I believe my infamiliarity with LISP was the biggest problem; I didn't
think that quote would not evalute anything, just not evalute the list
as a function.  However, what you are suggesting probably would have
helped me.  In fact, if placed with the Type Conversion section, I think
it would have solved my problem completely.

Oh, and does this list not set the reply-to header?

Patrick Niedzielski

reply via email to

[Prev in Thread] Current Thread [Next in Thread]