view libpurple/purple-send-async @ 22442:8460fd4c9b59

When Andrew was working on the memleak fixes, he pondered why buffer was declared as: char *buffer[16]; I changed it to char buffer[64] because 64 is 4 * 16 (I think? Someone should double check since I got 256 the first try). I don't know if 16 is a more proper buffer size, but changing it to 64 should make it behave more or less the same.
author Ka-Hing Cheung <khc@hxbc.us>
date Sun, 09 Mar 2008 21:42:27 +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