* Open file1.txt in sublime. This shows up as "file1.txt" in Sublime.

* In the terminal: mv file1.txt file1a.txt

* Back in Sublime it will show "file1.txt •" as if it's modified and unsaved. Saving that file will now recreate that file, and you'll end up duplicating the file and editing the wrong file.

Instead, what should happen is when you delete/rename file1.txt it should show "file1.txt (deleted)"

Try the same thing in any other editor (e.g. VSCode), and it handles it correctly.

The problem is that you can’t distinguish between a file that exists (where saving would overwrite the file) and a file that doesn’t exist (where saving would create the file).