• --new-instance
• open a new, separate instance of ST2 which used and closed with "File / Exit" without affecting any other ST2 instance
• --no-remembered-files
• open instance of ST2 which does not open _or save_ any remembered files

In combination, theses flags would allow better use of ST2 as the editor for various other programs (GIT, HG, etc).

Currently, I do use ST2 as the editor for GIT and HG, and I can obtain almost correct behavior for merging, editing commits, etc, by using:

sublime_text.exe --wait --new-window %S

This works, as I said, almost correctly. When I close the resultant window, control returns to the command line as it should unless I have ST2 already running and ("remember_open_files": true). If that's the case, then I must close the other program window (using either "File / Exit" or a second "File / Close Window" on the other open window) to get return of control to the command line.

It would be easier and much more consistent if I could open a new separate instance which doesn't open/save remembered files and which is always closed with "File / Exit". This would be my preferred syntax:

sublime_text.exe --wait --new-instance --no-remembered-files %S

Thanks for your attention.