Page 1 of 1

Away Messages don't execute Script items

Posted: Wed Feb 01, 2006 11:47 pm
by SenorMano
For quite some time, I was able to include the code to execute various scripts in my away messages. For example, I could put /pun into the text of my away message. When the auto-reply happened, it would execute the /pun using the appropriate AppleScript and the recipient would see the results.

After an Adium upgrade several months ago, it broke. Now, the user sees "/pun".

I've uninstalled and reinstalled the scripts.
I've redone the away messages.
I've tried both typing the /pun into the away message and insterting it using the Edit-->Insert Script.
The scripts work fine when I type them into an active chat message

Any ideas? I couldn't find anything in other posts, or in the trac.

Posted: Thu Feb 02, 2006 12:52 am
by Tipo 61
are you putting anything in front of /pun?

Also, try creating the away message with /pun all by itself, and enter the script by using: Edit -> Insert Script

Posted: Thu Feb 02, 2006 2:59 am
by Wengero
the scripts that use "/" cant do all the things that ones that use other other symbols like "%", i dont remember what they cant do but this could be one of the things. If you want to change the "/" to something else just right click on the xtra in ~/library/application support/adium 2.0/scripts and choose show package contents. Then find the .plist file and look for where it says /pun in it and just change that to something like %pun

Posted: Thu Feb 02, 2006 7:19 am
by SenorMano
Thanks Tipo & Wengero -

I did have text and a paragraph break before the script call.

Switching to the % seems to have solved it.

The strange part is that I changed nothing from before... the / worked fine with text in front of it. And all of the away messages were left over from a while back. Perhaps something in an incremental upgrade changed the handling of scripts or away message processing.

Posted: Thu Feb 02, 2006 12:43 pm
by Tipo 61
I think it did. A while back, they changed it because people were having problems with URLs (http://<someone's script name>) or something like that.