Mercurial > pidgin
view libpurple/purple-send-async @ 16702:56f0049d3207
Add padding to silc and bonjour to get rid of a bunch of warnings.
What's the reasoning behind this padding again? So that we don't
break binary compatibility across minor versions?
author | Mark Doliner <mark@kingant.net> |
---|---|
date | Mon, 30 Apr 2007 07:11:51 +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