Mercurial > pidgin.yaz
view libpurple/purple-send @ 20101:3a5f152e7ed0
This fixes compilation issues where old glib and either an old gcc or a
non-gcc compiler is used. I have opted to put the same preprocessor
directives in each plugin over including additional headers to fix this for
the purposes of staying as close as possible to the version I have in the
how-to documentss on the wiki. Fixes #3142 and bugs reported via the mailing
list, IRC channel, and XMPP conference.
author | John Bailey <rekkanoryo@rekkanoryo.org> |
---|---|
date | Mon, 17 Sep 2007 04:50:24 +0000 |
parents | 598b1b15b199 |
children | 942bf314fc8a |
line wrap: on
line source
#!/bin/bash METHOD_NAME=$1 if test -z "$METHOD_NAME" then cat <<EOF This program calls purple API functions using DBus and prints the return value. If you are not interested in the return value, use purple-send-async. 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 PurpleAccountsFindConnected string: string:prpl-jabber $0 PurpleAccountsGetAll $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 --print-reply --type=method_call /im/pidgin/purple/PurpleObject im.pidgin.purple.PurpleInterface.$METHOD_NAME "$@" echo