When a file changes somewhere else
Edit on another device or in another editor. Rescriptus merges what it can and asks only when it must.
Because your files are plain Markdown, you can edit them on another device, in another editor, or in GitHub itself. Rescriptus notices and brings the changes in.
How often it looks
With GitHub, Rescriptus checks your repository every 30 seconds while the page is open, and when you come back to the tab. Changes arrive without a reload.
When you are not typing in that file
If a file changes elsewhere and you have nothing unsent in it, Rescriptus simply loads the new version. No banner.
When you were typing in it too
Rescriptus compares three things: the version you started from, your version, and the other one. It then does one of these.
- Different words changed. The two sets of changes are combined, word by word. No question is asked, and nothing is lost.
- The same words changed. Saving that file is paused and a banner appears: "This chapter was changed somewhere else". Nothing has been overwritten. The label says Needs a decision.
Your choices
- Compare versions shows the two side by side, with changed words marked.
- Keep both saves your text as a copy in Notes, Conflicts and loads the other version.
- Keep mine replaces the other version with yours, after you confirm. On GitHub the other version stays in History.
- Using the other version sets aside what you typed on this device in a recovery store, not deleted.
If you are not sure, choose Keep both.
A chapter deleted elsewhere
If a chapter you have open is deleted somewhere else, Rescriptus keeps your text and tells you, with a way to put it back.
Two tabs, two devices
A chapter can be edited in one tab at a time. On two devices, expect the banner when you switch between them after typing in both. Finish in one place first.