I found that this problem occurs if the non-TextEdit editor uses safe saving 
(FSPathReplaceObject or -[NSFileManager replaceItemAtURL:...]), whereas 
TextEdit doesn't complain if the app just writes directly to the file. Filed as 
rdar://9978155.

--Michael


On Sep 19, 2011, at 2:26 PM, Boyd Collier wrote:

> I just tried going through the sequence of steps that you described and also 
> couldn't quit TextEdit.  Along the way, I got several possibly revealing 
> messages, one of which read "The operation couldn't be completed. 
> (GSLibraryErrorDomain error 1." and one that read "The document 'A.txt' is on 
> a volume that does not support permanent version storage."  When I have more 
> time, I'll try to provide more detailed information on exactly what steps I 
> took and what happened at each step.  I'm running 10.7.1 build 11B26.
> 
> Boyd
> 
> 
> On Sep 19, 2011, at 9:25 AM, Gerriet M. Denkmann wrote:
> 
>> I have a document called "A" which contains the string "A".
>> 
>> I open "A" in TextEdit.
>> I open "A" in some other editor, change the text to "AX" and quit the other 
>> editor.
>> 
>> I change the text in TextEdit to "AA" and try to quit TextEdit - but I 
>> cannot. Several sheets come up, telling me strange things (like "The 
>> document “A” is on a volume that does not support permanent version 
>> storage." - hard to believe), giving me several choices - but regardless of 
>> what I choose, I cannot quit (nor close the document).
>> 
>> Other than using Force Quit from Activity Monitor.
>> 
>> I am trying to understand the new Lion (10.7.1) autosave in place feature. 
>> Is this behaving as expected?
>> 
>> Kind regards,
>> 
>> Gerriet.

_______________________________________________

Cocoa-dev mailing list ([email protected])

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to