pidgin/pidgin

Make PurplePluginProtocolInfo definitions consistent
release-2.x.y
2020-05-20, David Woodhouse
159344ba2a49
file isExecutable
Make PurplePluginProtocolInfo definitions consistent

Since we can't use C99 structure initialisers, we have to manually add
new NULL fields to all protocols whenever we extend the structure.

Make it slightly easier to script that, by making the current last
field (get_cb_alias) consistent in all cases. In particular, there's
no reason *not* to have the trailing comma, as most already do.

Now I can add a new field to the PRPL by doing something like this...

PROTOFILES=`grep -rl '[A-Za-z_][A-Za-z0-9_]*,[[:space:]]*/\* get_cb_alias \*/' libpurple/protocols/ `
sed '/\/\* get_cb_alias \*\//{p;s/[A-Za-z_][A-Za-
#!/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 "$@"