I have a script that I run from Eudora’s script menu and, consequently, within Eudora’s realm. The actions taken by the script require that Eudora be quit and then launched. Unfortunately, I can’t handle this by quitting Eudora and then restarting her with the script since the script terminates as soon as the quit command is issued. I’m hoping to overcome this by sending a command, or commands, to the shell that will provide a delayed reaction. This would be sent to the shell by the Eudora script immediately before issuing the quit command, causing the shell script to wait and then launch Eudora.
Any advice on how to implement this delayed launch via ‘do shell script’ will be greatly appreciated. Oh, there’s one more gotcha. The Eudora script must not wait for a response from the shell commands since it seems to throw a monkey wrench into the whole process.
Why not just create a small helper app that your script calls just before it quits? This can be an FBO script that just looks for open apps, waits until Eudora is fully quit, then relaunch it, then quits itself. You could add this helper app inside a script bundle to make it even easier to distribute. No need to invoke the shell (though there’s probably a way to do what you want from the shell).
Yep, a helper app is probably the way to go. I was looking to the shell only for the sake of portability but I’ll explore the option of creating a bundle to hold the helper app (I’m not sure what’s possible in Jaguar).
I’m pretty sure the script bundles themselves are backwards compatible with 10.2.x but perhaps not the ability to make them. If you want some help with that, let me know (unless, of course, the code is run only in which case we’ll have to figure something else out).