Ampersand 0.8.0

New

• Your unsaved text survives a crash — Ampersand saves as you type, so the gap between a keystroke and the file is normally a fraction of a second. A crash, a force quit, or a power cut inside that gap used to take those words with it. That text is now kept separately on your Mac as you write, and let go of only once the file itself has been written. Reopen the document and a bar offers it back: Restore My Text, Compare… to see it beside what the file holds now, or Discard.
• A warning when a file changes underneath you — If something else rewrites a file while you have unsaved text in it — a sync client, a script, another editor — Ampersand stops saving and says so, because one of the two versions would otherwise be lost. Keep My Text, Use the File on Disk, or Compare… to see line by line what actually differs before choosing. Nothing is written until you do, and a file deleted out from under you can be written back.
• Open Quickly — Press Command-Shift-O and type part of a file name to jump to it, anywhere in your projects. It opens on the documents you had open most recently, so getting back to the chapter you just left is the shortcut and Return. You do not have to type the name exactly: chp3 finds chapter-3.md, as long as the letters are in that order. Arrow keys move through the list, Return opens, Escape closes.
• Unsaved Text in Settings — See what Ampersand is holding for you: which file each piece of unwritten text belongs to, where that file is, and when it was last held. Throw a single piece away, or empty the list. Anything left over for a file that no longer exists clears itself out after a week, so a document you deleted does not keep a copy of itself around.

Fixed

• Your Markdown is no longer reformatted as you type. In the Editor view, typing a single character used to rewrite the whole document behind the scenes: lines you had broken yourself were run together into one long line, the blank line at the end of the file disappeared, and table rows were re-spaced. What you saw on screen never changed, so there was nothing to notice until you looked at the file. Ampersand now remembers where your lines end and writes them back exactly as they were, indentation included.
• Line breaks you asked for are kept. A line ending in two spaces is a visible line break in Markdown. Anywhere but the first line of a paragraph, that break was being quietly turned back into an ordinary space, which changed how the document read.
• Quitting with a warning on screen no longer costs you the text. Quitting while a “changed on disk” warning was still waiting for an answer correctly refused to write — and lost the words with the app. They are now offered back the next time you open that file.