view libpurple/purple-send-async @ 20969:17ee8c81c99b

Only free the GString "alt" if it's non-null. This was causing an assertion failure when either sending or receiving a direct IM (or maybe both) with HTML logging on (and maybe other types of logging--I didn't check). Fixes #3514
author Mark Doliner <mark@kingant.net>
date Tue, 16 Oct 2007 07:31:41 +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.  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