view libpurple/purple-send-async @ 32315:c2fa3a76a0be

Get rid fo purple_strlcpy and purple_strlcat. These are convenience functions that call g_strlcpy and g_strlcat. They're only mildly convenient, though. And only used in one place. The reason I don't like them is that I think it's easy to use them incorrectly. It's easy to use the functions and not realize that they use sizeof() to determine the size of the destination buffer. I think it's too easy to accidentally use these functions with a string on the heap (which wouldn't work correctly).
author Mark Doliner <mark@kingant.net>
date Sun, 21 Aug 2011 01:04:31 +0000
parents cea56d000b16
children
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.  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 "$@"