Mercurial > pidgin.yaz
view libpurple/purple-send-async @ 23623:38a30596ff49
This looks good to me. I'm thinking we probably don't want to get
into the habit of documenting parameters when we make function calls...
that could lead to a lot of documenting. Somehow the header file
had the wrong name for this. And then some other whitespace/comment
changes.
author | Mark Doliner <mark@kingant.net> |
---|---|
date | Sun, 20 Jul 2008 19:44:24 +0000 |
parents | 942bf314fc8a |
children | 584063555949 |
line wrap: on
line source
#!/bin/sh METHOD_NAME=$1 if test -z "$METHOD_NAME" then cat <<EOF This program calls purple API functions using DBus. As opposed to purple-send, it does not print the return value. Usage: $0 method-name type1:parameter1 type2:parameter2 ... This shell script just invokes dbus-send, see man dbus-send for how to specify the parameters. Examples: $0 PurpleCoreQuit Use dbus-viewer to get the list of supported functions and their parameters. EOF exit 1 fi shift dbus-send --dest=im.pidgin.purple.PurpleService --type=method_call /im/pidgin/purple/PurpleObject im.pidgin.purple.PurpleInterface.$METHOD_NAME "$@" echo