Mercurial > pidgin

view libpurple/purple-send @ 26937:74c9f4f79825

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Add 'jabber' to the signals output and NULL checking so it won't crash on Windows I'm baffled, but I currently get this signal output for the jabber-receiving-message signal: (22:27:44) jabber: Recv (ssl)(307): <message from='paul.aurich@gmail.com/desktop35DEABC4' to='paul@darkrain42.org/Testing' type='chat' id='purpleabb8c602'><active xmlns='http://jabber.org/protocol/chatstates'/><nos:x value='disabled' xmlns:nos='google:nosave'/><arc:record otr='false' xmlns:arc='http://jabber.org/protocol/archive'/></message> (22:27:44) signals test: received message (type=chat, id=purpleabb8c602, from=(null) to=chat) (nil) presence and IQ are fine...
author Paul Aurich <paul@darkrain42.org>
date Fri, 22 May 2009 05:31:46 +0000
parents 942bf314fc8a
children cea56d000b16
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 and prints the return value.
If you are not interested in the return value, use purple-send-async.

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 PurpleAccountsFindConnected string: string:prpl-jabber
   $0 PurpleAccountsGetAll
   $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 --print-reply --type=method_call /im/pidgin/purple/PurpleObject im.pidgin.purple.PurpleInterface.$METHOD_NAME "$@"

echo