History and restoring

History comes from Git, so it is available when your project is kept on GitHub. You do not need to know Git.

Projects kept in this browser or in a folder do not have a history of their own. Rescriptus says so on the History tab. For those, download a copy now and then (see Choosing where your writing lives), and let a backup tool look after a folder.

Look at earlier versions

1. Open the chapter, wiki page or note.
2. Open the History tab.
3. You see saved versions, grouped by day, with the time and a short message. The latest 40 for that file are shown.
4. Open one to read it. You can compare it with your text now, with changed words marked, or read the full text.

A version appears once it has been sent to GitHub. The last few minutes of typing may not be listed yet.

Restore

• Restore this whole version makes that text the current text. You confirm first.
• Restore a passage brings back just that passage and leaves the rest of the text as it is now.

Before restoring, anything waiting is sent, so it is not lost. The text you replaced is itself saved in history, so a restore can be undone by restoring the one before it.

What you can restore

• Earlier text of a chapter, wiki page or note.
• A version removed with Keep this on an alternate.
• Text replaced with Keep mine after a clash.

Deleting

Deleting a chapter, book, wiki page or note shows an Undo button for a few seconds. After that, the file is still in your repository's Git history on GitHub, and you can bring it back from there.

Limits

• History is as detailed as your commits. Rescriptus sends changes in batches, so there is one version per batch, not one per keystroke.
• It shows the latest 40 versions of one file. Older ones are still in your repository.

Your repository

You can also see the full history on GitHub, with no limit, and use any Git tool.