From: Patrick Michael Niedzielski <patrickniedzielski@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Wrong type error in dbus method
Date: Mon, 05 Jul 2010 15:45:45 +0000 [thread overview]
Message-ID: <1278344745.3600.18.camel@patrick-pc-win> (raw)
In-Reply-To: <878w5qpaka.fsf@ambire.localdomain>
Hi,
On Mon, 2010-07-05 at 11:00 +0200, Thien-Thi Nguyen wrote:
> () Michael Albinus <michael.albinus@gmx.de>
> () 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?
Cheers,
Patrick Niedzielski
next prev parent reply other threads:[~2010-07-05 15:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-02 2:23 Wrong type error in dbus method Patrick Michael Niedzielski
2010-07-02 9:04 ` Thien-Thi Nguyen
2010-07-03 8:59 ` Michael Albinus
2010-07-05 9:00 ` Thien-Thi Nguyen
2010-07-05 15:04 ` Drew Adams
2010-07-05 18:34 ` Michael Albinus
2010-07-05 19:03 ` Thien-Thi Nguyen
2010-07-05 19:35 ` Michael Albinus
2010-07-05 20:40 ` Chad Brown
2010-07-05 15:45 ` Patrick Michael Niedzielski [this message]
2010-07-05 18:40 ` Michael Albinus
2010-07-09 19:47 ` Michael Albinus
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1278344745.3600.18.camel@patrick-pc-win \
--to=patrickniedzielski@gmail.com \
--cc=emacs-devel@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.