view libpurple/purple-send-async @ 32818:01ff09d4a463

applied changes from 444dec0882a9950944852a408a50904a458629bf through 1f233991b11d30d7bd9d1e058e19fe162a9600f3 Apparently, some random servers have decided to send us an annotation with no name, and the value isn't really self-describing either. Anyway, this empty name could cause a crash. Fixes #15126.
author Elliott Sales de Andrade <qulogic@pidgin.im>
date Sat, 02 Jun 2012 02:30:13 +0000
parents cea56d000b16
children
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 "$@"