Profile: David Blche (monoclast)
4 comments | |
0 xtras |
Latest comments
# by monoclast on 11/19/11 at 16:17:55
For the life of me, I can't get this extra to work on Lion. I'm using the latest version (1.1) - just downloaded and installed from your link above.
I've got Adium set up to use the "Pipe event to command" action for the "You connect" event, pointing to a Perl script at /usr/local/bin/adium_events.
The script has execute permissions, and runs fine manually from the command line. I have it logging out to a log file so I can see when it runs.
It never gets run from Adium when I connect.
I've also tried setting it to run this very simple command:
/usr/bin/osascript -l AppleScript -e "tell application "Finder" to beep"
Nothing happens when I connect. No joy. : (
I've got Adium set up to use the "Pipe event to command" action for the "You connect" event, pointing to a Perl script at /usr/local/bin/adium_events.
The script has execute permissions, and runs fine manually from the command line. I have it logging out to a log file so I can see when it runs.
It never gets run from Adium when I connect.
I've also tried setting it to run this very simple command:
/usr/bin/osascript -l AppleScript -e "tell application "Finder" to beep"
Nothing happens when I connect. No joy. : (
# by monoclast on 11/20/11 at 05:57:37
Is Adium responsible for closing STDERR and STDOUT? If so, why would Adium do that?
Is there a way I could somehow re-open STDERR and STDOUT in a Perl script?
Why am I able to echo things out to a file from a shell script (echo "blah" > file), but not print to a file (open FILE, print FILE "blah") in a Perl script?