Mercurial > pidgin.yaz
view libpurple/purple-send @ 24630:8f757b2139d2
String changes (a few of which I had already made, grumble grumble).
I tried to re-use strings that exist in other protocols as much as
possible. When calling purple_connection_update_progress() the strings
should not have ellipsis. When calling purple_connection_error_reason()
due to a keep alive timeout, do not include the number of seconds,
because there shouldn't be a reason for users to care
author | Mark Doliner <mark@kingant.net> |
---|---|
date | Thu, 11 Dec 2008 07:17:32 +0000 |
parents | 942bf314fc8a |
children | cea56d000b16 |
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 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