A refusal to save is almost always a protection. Balise reports a conflict rather than overwriting someone else’s work, including your own.
The file changed on disk after I opened it
What happens. Another application, script or Git operation changed the file during your session. Writing over it would erase that change unseen.
Your data is not affected. Your work remains in the window and the disk version is intact.
What to do. Balise opens a three-state comparison: the saved baseline, your local version and the version on disk.
Choose what to keep:
- leave the conflict undecided for now;
- reload the disk version, discarding your local changes;
- save your version under a new name, keeping both.
These actions never replace the disk version.
Balise can no longer write at the file’s location
What happens. The macOS permission for this location is no longer valid, often because the file or folder moved or was renamed.
Your data is not affected. The window’s content is intact.
What to do. First save a copy elsewhere, in a folder Balise can access. Then restore permission as described in When Balise can no longer read a file or folder.
This is a partial preview of a large file
What happens. Balise only loaded part of the file. Saving over the original would replace the whole with a fragment.
Your data is not affected, precisely because Balise refuses.
What to do. Export a segment or copy.
The document comes from recovery
What happens. A session marked Recovered deliberately has no write connection to the original file.
Your data is not affected. Keeping the original intact is the purpose.
What to do. First check that the recovered content is what you want, then choose File > Save As to select where to write it.