duplicate files upon save?!?

I believe this is Mountain Lion creating a tempoary backup file and is normal for other applicationsto do the same.

Yeah, it's a joke. To me, it seems like a teriible idea. Can anyone shed light on why you would want this to happen? For instance, this is supposed to be "save" not "duplicate". I am consistently frustrated by the tilde (~) auto save/duplicate process. I have finally found this one thread in which someone found this unsettling.

Is there anyway to remove this feature?

This is supposed to be a response to the original post by marsmars.

Me. too.

All apps with saveless documents are generating these dupes with tilde. They are adding up across my computer. Totally annoying.

you may want to respond directly to Appleabout this issue using Apple Support Feedback:

Apple Support Feedback

Check and check. I already have, hopefully there will be a revision come next release.

I was hoping there might be a workaround or a method to prevent or modify the behavior of these tilde '~' saves?

I reported it, too. Ad I was wondering about a fix/workaround as well, like maybe a Boolean switch that could be turned on/off in terminal.

That's really interesting, I've never done something like that but perhaps it is a simple switch.

I noticed that this auto-save/tilde process could not occur if the file was write protected. I was doing this with a Quartz Composer file in /System. There was a little message that appeared in the title of the program indicating it could not do so. Not that you'd write protect all your files but perhaps there is a simpler oceans that you could deny.

yeah. I am using Pages(4.2) and mountain lion(10.8.2).

I have the same problem.

I turn off the autosave and versioning with the tutorial here

https://discussions.apple.com/thread/4166543?start=0&tstart=0

and comp up with this problem

when i turn that on, the duplicate file won't generate, but the versioning is really annoying and use a lot of my space.

So, I can't find a way to solve this problem even now

😟

I thought I would provide some more information for anyone else who might run into this:

I was encountering precisely the same issue. In my case, I had deleted the Document Revisions database at the root of the drive to solve an unrelated problem with backups. I had assumed the database would simply be recreated the next time a file was saved in a versions-supporting application. This was not the case however. Apparently when an application is unable to save a version in /.DocumentRevisions-V100, it instead renames the current version of the file to "filename~" and saves a new version with the original name.

In my case, all I had to do to fix it was to restart the system. This caused the database to be recreated, and saving started working normally again. This is clearly not exactly the same as what the happened to the original poster, but the symptoms are the same, and I'm assuming the same basic cause (the OS is unable to save revisions to the revisions database.) If I were in the original poster's position and had not already reinstalled my system, I would try deleting the .DocumentRevisions-V100 directory, restarting, and seeing if this fixed it (WARNING: deleting this directory will remove all but the latest saved version of all your files)

To delete .DocumentRevisions-V100, open Terminal and enter "sudo rm -rf /.DocumentRevisions-V100"

Hopefully this helps someone.