-
Notifications
You must be signed in to change notification settings - Fork 7.6k
Warn user on external changes to saved files #12181
Comments
The relevant bits of code for this (do correct me if I am wrong): brackets/src/project/FileSyncManager.js Line 123 in afb5249
|
I think the check should be something like
My extension brackets-persistent-history does the option a) of the above, but only between closing Brackets or switching projects: if there has been outside changes when the file is reopened, CTRL+Z reverts the file to the last state before the external changes. |
Dreamweaver is smarter in detecting file modification by third party editors even before it was acquired by Adobe |
If I remember correctly, Dreamweaver was acquired by adobe 11 years before. |
I am not very sure about the year. When I first met with |
I'm newbie to opensource and would like to contribute to this issue. Can I pick it up? |
Brackets currently warns the user if an unsaved file is altered by an external program or process, but doesn't do the same if the file is in a saved state in Brackets. Any external change, even a
touch
on a saved file will be automatically and silently applied. This is a serious problem as it causes the file history to be lost without warning.The loss of history, however, should be considered normal if a file is externally altered and the external change warning is accepted (i.e., the user clicks "Reload from Disk").What happens to the history is open. Different editors treat externally changed history differently. TextPad clears the history if a saved file is altered externally and loaded from disk at the warning prompt, where as SublimeText appends the altered external version to the SublimeText history. SublimeText, like Brackets, also doesn't warn the user, but the history works as expected: the external changes become part of the undo history.
The problem is that the user doesn't even have a choice, and may not even be aware a saved file has been externally altered, and that the undo history is lost.
The text was updated successfully, but these errors were encountered: