Like I don’t have enough problems, suddenly I can’t save any files I’m working on. I also can’t run them cause I guess script editor must do an autosave before it can run. I quit and reopened script editor but its still not working. And the file is a local one. Any ideas what this is all about? I have not tried rebooting, I have other things running right now that I can’t interrupt, so I guess I’m done scripting for the night.
Maybe it’s a compile error due to some corruption. Try copying the code text to a new script and saving that.
This happened to me last week (although I don’t recall the specific error).
I did try saving to a new doc. That worked. But then when I edited it further, I got back to this error. Strange.
And after a little while, the problem seems to have gone away on it’s own. Strange bug I guess.
Glad it is working again.
But just to clarify for future reference, I didn’t mean ‘save as’.
I meant ‘select all, copy, new document, paste, save’.
Yes, thats what I did, the problem persisted. I’m just going to assume its a bug in the system.
One issue that I am aware of is the following.
Under certain circumstances, if a resource fork gets attached to an .scpt script, the resource fork can grow exponentially each time the script is saved.
Eventually, it becomes impossible to save it properly.
I usually edit AppleScript in plain text format, but since it needs to be saved as an .scpt file in order to be run from a disk image, I occasionally encounter this issue.
As a workaround, exporting without overwriting seems to help, or, as Mockman suggested, creating a new file and replacing it instead of overwriting the existing one appears to be a good approach.
The size of the resource fork can be checked using xattred from eclecticlight.
Although it is possible to remove resource forks using the xattr command, doing so may damage the structure of the script itself.
For this reason, I believe that saving to a different file rather than overwriting the existing one is the safer and more effective approach.
