Mercurial > pidgin
view libpurple/purple-send @ 21172:33da7f2a30e4
Manually fflush() files written with purple_util_write_data_to_file,
because apparently some filesystems (XFS) can and will leave bogus
file contents if we don't. For systems which don't have fileno(),
this involves closing and reopening the file.
author | Ethan Blanton <elb@pidgin.im> |
---|---|
date | Thu, 08 Nov 2007 19:49:12 +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