Re: Applescript in the future
Re: Applescript in the future
- Subject: Re: Applescript in the future
- From: Alex Zavatone <email@hidden>
- Date: Thu, 23 May 2013 09:59:22 -0400
On May 22, 2013, at 9:09 PM, Christopher Stone wrote:
> On May 22, 2013, at 19:40, Shane Stanley <email@hidden> wrote:
>>> On 23/05/2013, at 10:28 AM, Alex Zavatone <email@hidden> wrote:
>>> What is failing is TextEdit and it appears to be a sandboxing issue.
>>
>> It sounds more like you're using a path rather than a file in the save command. This saves a TextEdit file outside its sandbox here here:
>
> ______________________________________________________________________
>
> Hey Alex,
>
> Shane's probably right on this one.
>
> We fought with TextEdit a bit back when Mountain Lion came out. TE1.8 is a little more touchy about the syntax you use when saving.
>
> I keep 1.6 on my ML system (which works fine) and zip 1.8. TE1.8 is a sluggish little beast, and I don't like it at all (but I keep a copy around for testing).
>
> BTW - if you're creating plain text docs why aren't you using TextWrangler? It's far more controllable via Applescript and much better behaved.
Because when I wrote the script back in 2010, TextEdit was good enough and was very consistent over its release history. I just build a string, plop it into a window so that I can debug the results and then save as a file.
With this in mind, I need to keep old copies of the TextEdit source that was delivered with the older versions of Xcode, or at least just put together a small editing app that I have the source to. IIRC, one of the most straightforward tutorials in Xcode 3.1.3 was to create a simple text editing app. Might not be a bad idea to have that around.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden