You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When closing a document, it would be nice to warn the user that the changes he made to the document will be lost.
I though QLMarkdown was an editor and I repeatedly hit ⌘+R to visualize the changes and ⌘+S to save them when happy. And I discovered that all my edits were lost without any warning upon closing the document.
I later found out that QLMarkdown is not an editor, and that's fair enough as long as it does warn me about it.
It would be nice if instead of just warning the user QLMarkdown offer to save the changes in the same file.
The text was updated successfully, but these errors were encountered:
When closing a document, it would be nice to warn the user that the changes he made to the document will be lost.
I though QLMarkdown was an editor and I repeatedly hit ⌘+R to visualize the changes and ⌘+S to save them when happy. And I discovered that all my edits were lost without any warning upon closing the document. I later found out that QLMarkdown is not an editor, and that's fair enough as long as it does warn me about it.
It would be nice if instead of just warning the user QLMarkdown offer to save the changes in the same file.
The command+s shortcut is for saving settings. The editor panel at the bottom is for previewing settings.
When closing a document, it would be nice to warn the user that the changes he made to the document will be lost.
I though QLMarkdown was an editor and I repeatedly hit ⌘+R to visualize the changes and ⌘+S to save them when happy. And I discovered that all my edits were lost without any warning upon closing the document.
I later found out that QLMarkdown is not an editor, and that's fair enough as long as it does warn me about it.
It would be nice if instead of just warning the user QLMarkdown offer to save the changes in the same file.
The text was updated successfully, but these errors were encountered: