view src/gaim-send @ 11261:b53606580f68

[gaim-migrate @ 13439] Patch #1226486 from Levi Bard Fixes bug #1224178 If you change the topic in a chat room and that topic change is rejected, the topic field is wrong -- it shows the new topic even thought it didn't get set. This patch resets the GUI's topic immediately when you hit enter. Then, if the topic change is successful, the server will echo the topic change back to us and we'll update the GUI to the new topic. The only question is, does the server always echo the topic back to us? From the core's point of view, I'm ready to assume yes. It's the case for both IRC and Jabber*. If someone could test changing a topic in SILC or Zephyr, that'd be great. If servers using those protocols do not echo the topic back, the prpl will have to fake it as appropriate. * I didn't actually test on Jabber, but Nathan said the server will echo the topic change back. If it's broken, let me know. committer: Tailor Script <[e-mail]>

#!/bin/bash
# 
# A little shell script for communicating with gaim using dbus

METHOD_NAME=$1

if test -z "$METHOD_NAME" 
then
    cat <<EOF 
This program uses dbus to talk to gaim.  If the gaim is not running and
the dbus engine is set up correctly, a new instance of gaim will be started.

   Syntax: gaim-send method-name parameter1 parameter2 ..."

This shell script just invokes dbus-send, see man dbus-send for how 
to specify the parameters.  

Examples:

   gaim-send Ping 
   gaim-send Quit
   gaim-send GetBuddyList
   gaim-send GetBuddyProperty int32:5 string:alias
   gaim-send StartIMConversation int32:5

See src/dbus-services.xml for the list of supported operations.  
EOF

    exit 1
fi

shift
dbus-send --dest=org.gaim.GaimService --print-reply --type=method_call /org/gaim/GaimObject org.gaim.GaimInterface.$METHOD_NAME "$@"

echo