0-byte file (again) - note completely destroyed

[luckman212]

Followup to your other points @WhiteNoise :

A safety net is implemented. It’s the file recovery. You can lower the interval to 1 minute if you like.

It’s already at 1 minute.

If a file cannot be saved, you will already get popup warning.

I have never ever gotten one of these. What do they even look like? If the problem is occurring during Obsidian’s quit/cleanup routines, how would this even be shown?

I noticed in another thread that you get the file merge popup. Maybe some other program is the source of your problems?

I haven’t gotten a file merge conflict in a while and in this case most definitely did not.

What you are proposing will make the current merge approach of external changes not possible, because the file can be different due to a benign external change.

I realize that, but again this could be made much safer with 2 changes:

1. never just blindly accept a change which truncates the entire file - at least not without making an immediate safety snapshot regardless of the user’s snapshot interval
2. a toggle to completely disable auto-external merging, as is being discussed over in Editor: Add a toggle to disable automatic merging of changes (non-obsidian sync)