Thanks for your reply, and for the link. I wasn't aware of this AppleScript issue with nested scripts. However, I don't remember having this kind of problem with the old BBEdit 9 or 10 that I used with these same AppleScripts. I'll try to group my different scripts into a single large script.
Le lundi 7 avril 2025 à 13:36:39 UTC+2, Ulrich Kapp a écrit : > This looks to me like a common problem in AppleScript. > AppleScript doesn't support multithreading. This means that if you run an > AppleScript from within another, the calling script is stalled until the > other is terminated. > So if your second script goes into an endless loop or hangs on any other > reason, you won't get any message at all, it's just the end… You can't even > terminate the calling script and often you have to "kill" your Application > by brute force. > > Maybe you can find some helpful information here: ⇨ macscripter.net > <https://www.macscripter.net/t/can-an-applescript-run-another-applescript/51489> > > Ulrich > Zax schrieb am Montag, 7. April 2025 um 13:20:28 UTC+2: > >> When an Applescript launched by BBEdit attempts to launch another >> Applescript, all BBEdit menus become *disabled* without any error messages >> (and then the only way to quit BBEdit is to force-quit). >> Using "try catch" or "with timeout..." don''t change anything. >> >> Sorry if this bug have already been reported. >> > -- This is the BBEdit Talk public discussion group. If you have a feature request or believe that the application isn't working correctly, please email "[email protected]" rather than posting here. Follow @bbedit on Mastodon: <https://mastodon.social/@bbedit> --- You received this message because you are subscribed to the Google Groups "BBEdit Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/bbedit/29c8fbfa-9d5a-4118-afac-ff5e104213ddn%40googlegroups.com.
