Mercurial > pidgin

view libpurple/purple-send-async @ 17664:8ee3fd09a543

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Remove lots of debugging statements, no longer needed. Along with 172d2f1fc811dba4cf65d127b27a799d1e121b58, this patch (I believe) fixes #193. The problem was that msim_close() was being called twice. Removed spurious calls, and no longer appears to crash. This now works: * Login with an invalid password. * `Protocol error, code 260: The password provided is incorrect.` (good) * Disable, and re-enable account. * Receive the same error message (good, no crash). * Repeat previous two steps ''ad nauseum'', with no crash. Closes #193.
author Jeffrey Connelly <jaconnel@calpoly.edu>
date Mon, 25 Jun 2007 05:24:44 +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