view libpurple/purple-send-async @ 22767:d5b3afea8764

After trying the available SASL mechs, jabber_auth_handle_failure() now proceeds to regular error handling instead of falling through to a final attempt with no remaining SASL mechs. Also, when removing a SASL mech from the js->sasl_mechs string, remove its preceding space, as well, so we can easily see if the string is empty just by checking its length.
author Evan Schoenberg <evan.s@dreskin.net>
date Fri, 02 May 2008 22:50:13 +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