I saved a iWork Numbers document as a template (and if I look at the file's file information in Finder, the template checkbox is checked). I later opened this template document on computer A and filled in some values. I didn't even actively save it (but Numbers automatically saves document continuously). Next I opened the same template from computer B - and lo and behold, the values I had entered at A appeared on B!?!? I thought templates worked by forcing the application to create a new "untitled" document based on the template that you by default saved under another name than the template. In other words, if you double click a template in Finder ten times you will have ten identical documents in Numbers named Untitled 1 to 10 based on the template (e.g. with some values and formulas prefilled), but that doesn't seem to be the case. **How are template documents supposed to work? How do I achieve what I describe above - i.e., create untitled documents based on an existing document without altering the original file?**

I'm trying to help a colleague whose MacBook periodically switches off without warning (I've had similar problems on a Mac Mini, so it's not power related). While investigating the logs in Library/Logs, I found a file talagent.log with something very odd, last updated very close to the time the computer last switched off without warning: Time Bundle ID Status Comment 0.000 - - TALagent Started (system uptime: 238.18 sec) 0.007 - - Liveness: 0 -> 1 (run_as_server) 0.038 - - Successfully read encryption key from keychain in 0.030809 seconds 15.007 - - Liveness: 1 -> 0 (__run_as_server_block_invoke) 15.007 - - Exiting out of boredom What the heck is talagent and what does it mean that it is **"Exiting out of boredom"**? I've read this thread but it doesn't help me understand what's going on here. My first thought was that it must be a virus, because that's such a non-professional thing for a log entry to say, but that linked thread seems to imply it's not such a concern; but it doesn't help me understand what it is or what that means. We use Symantec as a virus scanner, and the Mac in question is on Mavericks (can't currently update for unrelated compatibility reasons).

I hate the automatic saving and versioning in Mac OS X Lion. Is there a way to completely turn it off? (This has been asked before here , but the answer and the linked article are completely wrong, so I thought I'd try again.)

I'm looking for a foolproof way to edit a text file and be certain that the application or mac OS doesn't save a copy of the content, e.g. through some autosave function, or caching. The reason being I am storing sensitive information. The way I want to secure it is by placing the text file in an encrypted volume created and mounted with Vera Crypt. But as I did this I realized that certain text editors create autosave files. Are there any text editors, or other ways, to ensure I don't end up leaving traces of the text file, or its content outside of the encrypted volume?

I recently recorded a session with my dad. I stopped the recording after the session ended (with the setting set to save to Desktop), clicked the icon that appeared on the lower right corner to open the file, and played back a few minutes to make sure it worked. I then clicked Share to send it via AirDrop to my computer, which did not work; the status remained "cancelled" despite my efforts. I assumed I'd be able to access it through my phone by sending it through a third app, so I pressed cancel on the AirDrop pop-up window. The entire screen recording closed and (apparently) vanished forever after the action. I'm extremely frustrated because I can't seem to locate this video.

Since I got a new computer, I'm getting the following message all the time in TeXShop (same version I had on my old computer): > The document could not be autosaved. You don't have permission. This means my documents aren't being autosaved for some reason. But it gets worse. When I try to save a document, a lot of the time I get the following message: > The document "[documentname]" could not be saved. The file is locked. Do you want to save your changes to it anyway? If I click on "Save anyway", I get the following message: > You don't have permission to save the file "[documentname]" in the folder "[foldername]". To view or change permissions, select the item in the Finder and choose File > Get Info. I have all of my personal documents on custom folders in my iCloud Drive. All of my folders and the documents therein have permissions set up such that I can read and write. (The answers [here](https://apple.stackexchange.com/questions/37238/the-document-x-could-not-be-saved-you-don-t-have-permission) and [here](https://apple.stackexchange.com/questions/70421/the-document-x-could-not-be-autosaved-you-don-t-have-permission) are therefore useless to me.) I've also checked the permissions of ~/Library/"Autosave Information", and I can read and write there as well. I didn't have this problem *with the same files* on my old computer. I migrated everything to my new computer with Time Machine, which shouldn't mess with permissions, but, as stated above, I've checked my permissions anyway and they're fine. I don't know whether the problem is a Monterey issue (I had Catalina on my old computer), an Apple-Silicon issue (current computer is M1 Max, previous computer was Intel) or something else. Please help.

I just recorded a quicktime video but I closed my lid before stopping it. Now it isn't saved! Is there a way to recover this very important recording? This is empty: ~/Library/Containers/com.apple.QuickTimePlayerX/Data/Library/Autosave Information/

I know how to find unsaved TextEdit documents ordinarily. However, my computer's hard drive ran out of space and I have many open that are not autosaved anywhere as a result. I was using another app (Notes) and when I exported to PDF it made the app unresponsive. I force quit the Open and Save process that was showing as unresponsive and tried again. And I had the same result. So I tried using TextEdit (where I have over 300 documents open...bad idea I know) to export this text I needed to save as a PDF. I badly assumed the problem relating to exporting was just with notes. But when I tried to export, it also caused the app to become unresponsive. And force quitting the Open and Save process doesn't help. I was able to copy the files that are autosaved from the AutoSave folder, but there are about fifty that are not autosaved due to the HDD having been low on space when they were created. Is there a way to capture them from where they are running in RAM?

I don't know how but I get to see a lot of auto clipping files being generated on my desktop screen. This is how my desktop looks

I am getting the following error: > The document could not be saved. You don't have permission The error is not helpful at all because it does not point to where I don't have permission. To save the file, I need to Duplicate it each time, which is very painful. This time the error is from CleanWriterPro, but I have also received it from Numbers and TextEdit. Saving with TextMate works fine. Permissions to the file are set up correctly according to Finder. I think this must be some kind of problem with AutoSave permissions but despite googling with the error, I have not yet figured out what's wrong. I found one possible culprit for this problem for me: grant:Library joneskoo $ pwd /Users/joneskoo/Library grant:Library joneskoo $ ls -lad Autosave\ Information/ drwx------ 2 root staff 68 Sep 25 2010 Autosave Information/ Since Library is hidden in Lion, it needs to be made visible before the permissions can be fixed in Finder: chflags nohidden ~/Library After unhiding the Library, I opened the Get Information for Library, clicked the lock and selected "Apply to enclosing items" so that all files in Library made owned by me and no permissions for others. However, CleanWriterPro is still not able to save the file in Documents, even though I repeated the step for Documents and Desktop. I could not reproduce the problem in Numbers now. Repairing Disk permissions did not help. Possibly related: I can't even rename files in Finder now under Documents without typing my password. Techrepublic: [Introduction to OS X access control lists](http://www.techrepublic.com/blog/mac/introduction-to-os-x-access-control-lists-acls/1048) . grant:~ joneskoo $ ls -led Documents/ drwxr-xr-x+ 44 joneskoo staff 1496 Jan 17 06:55 Documents/ 0: group:everyone deny delete I don't know what introduced that ACL, Finder? How can I remove it? The question is: **what are all the places I need to check to fix this problem?**

When opening a PDF in Yosemite's Preview.app, I can select text using the Text Selection tool from the Markup Toolbar. However, if I don't click directly on the text, a blank text box will appear. For some reason Preview thinks I want to add an annotation everywhere I click even though I have not selected the Text tool. This is a problem in that it signals an edit to the document, thus changing the modification date and creating an auto-saved version with no meaningful changes. In previous versions of OS X, I could have solved this problem by using: defaults write com.apple.Preview ApplePersistence -bool no. Yet this does not seem to have an effect in Yosemite. Any workarounds?

My dad is using my old MacBook that I used when I was studying web design and I see that the laptop still autosaves all .js files. It's kind of cluttering the computer but I can't seem to find a way to disable it. I used Visual Studio Code when I was coding so maybe the answer is somewhere over there. If anyone might have an idea, all help is welcome

Being an avid Linux user prior to buying a MacBook Pro, I typically have several terminal tabs open at any one time. In the past, crashes and reboots would generally trash my workflow, and the majority of my respective tab histories. I searched for ways to solve this problem but always came up empty; aside from various techniques that utilised combinations of tools like ssh, screen, tmux, and required a virtual private server (or similar). One of my favourite things about using my MacBook Pro for writing scripts, and using CLI tools, etc; is that my terminal sessions persist beyond crashes and reboots by default. In fact, I just restored a backup from almost 2 years ago, and when I logged in for the first time, I was presented with my old desktop and three bash shells that comprised a project that I was working on all that time ago. I would like to know how OS X makes this feature possible. Does anybody here have insight into how it works?

Every now and then, some application (usually TextEdit) starts showing dialogs like this when I try to close or save any document: > **The document “2.txt” could not be autosaved.** > > Your changes will not be saved until the problem is resolved. You can also duplicate the document or discard your changes to close it. I'll have to quit and reopen the application in order to save anything again. - I have disabled both Resume and locking files automatically in System Preferences - The files have usually been in normal folders under my home folder and there hasn't been anything special about them as far as I can tell - I have tried repairing permissions - TextEdit's code signature is valid system.log usually has usually contained messages like this: 5/8/12 9:04:01.358 PM [0x0-0x17b17b].com.apple.TextEdit: [ERROR] GSLibrary.c:_AddGenerationInternal:393 Failed to consume sandbox extension; error 12 (Cannot allocate memory) 5/8/12 9:04:01.361 PM TextEdit: NSFileVersion tried to tried to add a new generation and failed. Versioned file URL: file://localhost/Users/lauri/Notes/2.txt, contents URL: file://localhost/Users/lauri/Notes/2.txt, error: Error Domain=GSLibraryErrorDomain Code=1 "The operation couldn’t be completed. (GSLibraryErrorDomain error 1.)" UserInfo=0x10b24d070 {} 5/8/12 9:04:01.362 PM TextEdit: NSDocument failed to preserve the old version of a document. Here's the error: Error Domain=GSLibraryErrorDomain Code=1 "The operation couldn’t be completed. (GSLibraryErrorDomain error 1.)" UserInfo=0x10b24d070 {} Failed to consume sandbox extension; error 12 (Cannot allocate memory)? Does anyone know what's going on here? Edit: I haven't seen those errors after I replaced TextEdit with [TextEditPlus](https://github.com/jjgod/TextEditPlus/downloads) . It's based on TextEdit's source code but it disables sandboxing and makes a few other changes.

When I close the lid of my Macbook Pro (Lion), it goes to sleep, which is good: it powers down without closing my applications. But if I just leave the computer unattended for a while *without* closing the lid, it attempts to **shut down** instead. It usually fails at this, because there's often a program such as Photoshop (which doesn't use Lion's autosave feature) blocking shutdown with a "Save as" dialog. But it does always succeed, annoyingly, in closing my browser etc. It does this even when the computer is plugged in and fully charged. When I leave my computer unattended for 15 minutes, I want it to behave exactly as if I had closed the lid: it should go to **sleep**, not shut down. How can I do this?

I ran into this problem today while writing code. Whenever I open a source file in Xcode, make changes and save them, the file will be copied to the "autosave information" folder and the references in the source tree view (command + 1) are changed to the new location. Right now I cannot edit files "in place" but have to edit them and copy them back from "autosave information". The code files are in a folder within "Shared" (my local "GitHub" repository folder to be exact). The account I'm using to edit the files owns them and has r/w-permissions. On another account which doesn't own the files but has r/w-permissions the problem doesn't occur. My Mac is a MacBook Pro Retina 15" 2014, 2,2 Ghz i7 running OS X 10.10.5. Does anybody have an idea what's wrong and how to fix it? --- **UPDATE** So, I found out two things 1. it happens with files outside of the "GitHub" folder in "Shared" as well 2. it only happens if I open a window in XCode and add files (the file I open first is saved in place, the added files are saved in "Autosave Information") Removing ACL permissions didn't help.

Imagine you have **Time Machine** running with Yosemite. You open **TextEdit**, create a new text document in which you actually write stuff. You can turn off your computer, restart it, the document will still be there. But you never saved it once, never. It's just a draft that gets saved as a draft (where?) - when you log out. Then if you close the window, and lose this document, I assume there's a copy of it somewhere since every time you turned your computer off and on again, the document was there! But... where would you now look for it in Time Machine?

I work in marketing and have several Gmail accounts established exclusively for my clients advertising programs that I must access frequently. Until a few days ago, each time I opened any Gmail account the User ID (Gmail address) and password have remained saved and would populate as I entered the first character of the Gmail address I was attempting to open. When a colleague asked me to open her Gmail account during a time when her system was down, I unintentionally clicked "never for this Web site" when Safari asked if I wanted to save her logon information and password. I realize now that I had clicked the wrong option and since that time none of the Gmail accounts are saved requiring that I enter the full address and password each time. I've followed the instructions on the help menu but nothing has worked. I use Safari version 6.0.4 and Mac OSX version 10.7.5. Any suggestions would be appreciated.

In my ~/Library/Autosave Information/ folder on 10.7, I have some fairly routine-looking files—a few unsaved scratch documents in applications that use Autosave, and accompanying plists for those apps. I also have 3 folders with names like 64FE2D0E-7447-4086-B7CA-8D59ED769875.genstore.noindex. They each contain a .genstore_lockfile file and a .genstore_staging/ directory, which contains another directory with a random name such as rneN5zs, which contains a single file, staged. The problem is that the staged files are pretty big - 1.49 GB, 980 MB and 312 MB. According to the Finder's timestamps, they were created back in June, and haven't been modified or accessed since. I'd like to free up that space on my drive if possible, but I don't want to go deleting these files without understanding what they are. The names and access times suggest they might be temporary storage for saved state data (although I'm not sure why it would be so big) that didn't get cleaned up. Running lsof doesn't list any process accessing those files. Does anyone know what these files are? Do you have similar ones on your system? Can they safely be deleted?

Just wondering how, if at all, Versions on Pages for Mountain Lion (10.8) works with iCloud, specifically in relation to iOS 5 devices. My own testing seems to indicate that a Pages document created on the Mac saves versions in iCloud that you can revert to but only on the Mac (can't find an iOS interface for Versions). However, if I create a document on Pages for iOS (forcing an upload to iCloud after each edit) I can't revert to previous versions made on iOS, even on the Mac. One time, when I tried to do this, I saw a message saying the file is stored on a volume which doesn't support permanent version storage. However I have been unable to reproduce this message. Can anyone enlighten me as to how Versions is supposed to work with iCloud? Is it a Mac-only feature, not available on iOS? If so, how best to guard against unwanted edits on iOS? Should I just prevent the doc from being uploaded to the cloud until I am happy with it, and use the undo / redo feature? As I understand it, we only have Versions on the Mac because we also have Autosave. On iOS all saving (to the cloud) is done manually (the equivalent of the old command-s on Snow Leopard) thus eliminating the need for iOS versions. Have I got the correct picture here? Sorry for the long post! I'd really appreciate any replies.