Tisty writes to and reads from the folder you chose. What uploads that folder is your provider's own program — Google Drive, OneDrive, iCloud, Dropbox, Syncthing — not Tisty. If that program is not running, Tisty will keep saving your work fine and will have no way to tell that nobody is picking it up.
Go through this in order. The first three cover almost every case.
This is the usual cause, and the easiest to miss: all it takes is for its start-at-login to be off and for you to reboot one day.
- macOS — look for its icon in the menu bar, top right. If it is not there, it never opened.
- Windows — check the system tray, next to the clock; expand the arrow for hidden icons.
Open it and give it a few minutes.
An open client is not always syncing. Check in its own panel that it does not say paused, that the account is still signed in, and that you have not run out of space.
Many clients let you choose which folders go up. If the one you gave Tisty fell outside that selection, everything works except the one thing that matters.
Changes travel through the folder, so the other machine has to open Tisty to pick them up. While it is off, your work waits up there.
In Settings → Data there are two dates that do not mean the same thing:
- My last round — when Tisty read and wrote in the folder. This one being current does not mean anything was uploaded.
- Something last arrived from another machine — when something genuinely came in from another machine. If it has been still for days and your machines are on, that is where the problem is.
The Open the folder button shows it in your file browser. Look there for your recent files, then check with your provider — from its website, say — whether they are up there too. That comparison is what answers the question.
Try Settings → Data → Send everything again. It copies everything of this machine's to the folder again without asking whether it is already there, which is exactly what you want when a cloud client skipped a file.
Because it cannot know. Tisty talks to no cloud: it has no account of yours, no credentials, and no idea which provider — if any — is behind the folder you named. It leaves the files there, and there its reach ends.
It could ask your provider's program, and it may one day. Today it does not, so it shows you the facts it does know instead of a verdict it cannot back.
No. Your work is complete on the machine where you did it, and Tisty's log only appends: nothing is overwritten or dropped. As soon as the folder starts moving again, both machines catch up on their own, even if both were working at once.
Tisty's editor writes Markdown back out, and a few shapes do not survive that trip: front matter, footnotes, links written by reference, blocks of HTML, HTML comments and entities, whatever a code fence says after its language beyond a name, and a list item that opens on a block — a quote, a fence, a heading, a picture or another list where its first line should be text. Rather than open the document and quietly destroy those on your first keystroke, Tisty says so and opens it for reading.
The bar at the foot offers to convert it — which rewrites the document into what the editor can keep, and keeps a copy of how it was beside the documents. If the conversion cannot get all of it, you are not stuck: Edit it anyway opens the document with the warning left in view, so you decide what is worth losing.
No. A code block whose language is mermaid draws its diagram, and one that
says math sets its formula, and both are drawn by code that ships inside
Tisty. Nothing is fetched, no font is loaded from anywhere, and it works with
the network unplugged — same as everything else here.
Both stay Markdown. GitHub draws ```mermaid and ```math too, so the
document reads the same anywhere else.
In how long the rule under the header is drawn. Markdown has nowhere to keep a column width, so Tisty writes it as the length of that column's dashes and reads it back the same way — a wider column, a longer rule. Every other Markdown reader ignores how many dashes there are and draws the table just the same.
It is written in steps rather than to the pixel, and a column narrower than 40 or wider than 1200 pixels is kept at that bound. A table nobody has resized is written with three dashes, exactly as before, so nothing you already have changes.
Only over the version it read. When an assistant reads a document it is handed a print of that exact text, and replacing the body whole requires sending that print back. If you wrote in the document in between, the print no longer matches: nothing is written and the assistant is told to read it again. What it did replace is kept beside the documents either way.
The window tells you when something wrote in the document you have open, and if you try to save over a change you had not seen, it asks which one stands.