Can't quit Manuscripts 1.0

---

Hi,

When I attempt to quit manuscripts with an unsaved document and click 'Revert changes', assuming that Manuscripts will discard unsaved chages and close the program, instead it closes and then reopens the same document, and does not quit Manuscripts. The only way to quit Manuscripts appears to be to save the document.

Cheers,
Oliver.

@olibclarke the "Browse Earlier Versions" feature and in particular the "Revert" feature is not intended to be used to close the app, but it's used to jumping to earlier versions of the document (in case you want to get back to even weeks old versions of your document). Apple's documentation on the document versioning is quite helpful in understanding what's going on: https://support.apple.com/en-gb/HT202255.

You can close the app simply by choosing File > Quit (⌘+Q).

@mz2 That is exactly what I was doing - I was using File...quit, and it comes up with the dialog asking me whether to revert changes, save or cancel. If I revert, the document closes and reopens. If I save, the document is saved (which is not always what I want) and if I cancel, nothing happens obviously. The only way i can find to quit without saving seems to be to force quit the app, which is strange.

@mz2 This is still an issue in 1.1.3. When quitting a document with unsaved changes, Manuscripts often gets stuck in an infinite loop of "Revert changes"--> quit manuscripts --> Manuscripts opens same document again --> rinse and repeat. Only way to avoid is to force quit or to save the document.

@olibclarke thanks for the reminder. I've taken a note of this – I'm 90% sure I know what this is about.

@mz2 this still happens in 1.1.4 - any progress on a fix?

@mz2 this still happens in 1.1.5. 9 months later.

@olibclarke are you perhaps saving documents on some volume that does not support document versioning and autosaving, or have you turned off auto-save globally in the OS? The reason this goes unresolved still is I am simply unable to find the conditions where this would happen. The dialog that comes up with unsaved changes includes a "Delete" and a "Save" option. Pressing "Delete" works normally whenever I've tested this. I'm missing some factor here, any further context would be much appreciated!

The re-opening happens because the reversion behaviour in the app is geared towards the File > Browse Earlier Versions. I simply need to find the instance of where this is triggered in an unwanted fashion and make it not happen except when you use File > Browse Earlier Versions.

@mz2 neither, to my knowledge. It happens every time. I don't get a dialog with "Save", "Cancel" and "Revert Changes". I am using a MBP 13" (early 2015), with OS X 10.11.5. What other details can I give you?

@mz2 sorry, meant to say I don't get a dialog with "Delete" and "Save" - instead, it has "Save", "Cancel" and "Revert Changes"

@olibclarke what kind of volume are you storing documents on? iCloud Drive? Just your regular home directory? Is it on your local computer or is it for instance a network volume or a USB drive?

@mz2 Local computer, in my dropbox folder.

@olibclarke thanks – so definitely not that then, assuming your Dropbox folder is located on your startup disk volume as it typically is. In System Preferences, do you have "Ask to keep changes when closing documents" toggled on or off?

@olibclarke ah, now we're talking! I found this hidden way to cause the state you are describing:

defaults write com.manuscripts.Manuscripts ApplePersistence -bool no

This disables the automated document saving behaviour, which I have no idea how to make happen from anywhere with a graphical user interface in OSX? I believe I now have what I need to fix this. Thanks for your patience!

@olibclarke can you confirm meanwhile that applying the following in the Terminal (whilst Manuscripts is not runningn) re-enables the autosaving behaviour by which you'll see the "Delete" / "Copy" behaviour?

defaults write com.manuscripts.Manuscripts ApplePersistence -bool yes

@olibclarke I believe this should now be resolved for the next 1.2 beta (we're versioning those 1.1.x still – it'll be 1.1.5-…). The OS provided behaviour with autosaving is cryptic to say the least, and I was only able to reproduce this for a moment. I'm pretty confident though that the problem really is resolved.

Hi @mz2 - unfortunately, after entering this command and launching manuscripts, the behavior still persists.

@olibclarke OK. This may be the case if you have multiple copies of the app on your disk at different locations. At any case, the next beta should indeed resolve this. Thanks again for reporting this and thanks for your patience.

Hi @mz2, that should not be the case, I only installed Manuscripts once (in /Applications) and then updated in-app. Thanks for taking a look.