Mercurial > pidgin
view libpurple/purple-send @ 23010:2b91ea8c94d5
Rearrange some of the HTTP proxy handling to make sure that we're actually
connected to the proxy server before calling the callback (in the case where
we were trying to bypass CONNECT tunneling, that wasn't happening).
Thanks to dasvo for tracking down what was happening. Fixes #5057.
author | Daniel Atallah <daniel.atallah@gmail.com> |
---|---|
date | Tue, 20 May 2008 19:49:26 +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