save_on_focus_lost saves files when focus is lost, not only from sublime, but also when you switch to other files inside sublime, so I don't understand how can you have unsaved changes anywhere else except on the current file.
In my workflow, I make some changes to several files, then run a build and test run in an external window. If each file is saved on loss of individual focus, then I have to wait until my long test run finishes before trying something else, lest I break the run by changing a file and then switching to another file, thereby saving it. If I had point-in-time consistent saves on loss of focus, I could save all files and continue making changes without worrying about corrupting the existing run.
The title and comments are misleading.
The issue here is adding an option to change what triggers lost focus event.
Ahhh I apologise — thanks Jon — that's just what I need.
I hadn't noticed that setting.
Thanks very much!
Служба підтримки клієнтів працює на UserEcho