0

Ignore empty configuration files

cpf 7 years ago • updated by mike henken 7 years ago 1
I went to create a configuration file, selected the wrong menu item, somethingorother happened, and I ended up with an blank .sublime-settings file. 

The next startup, ST2 displays an error ("Error trying to parse settings") then "crashes." It doesn't actually crash though, it stays running in the background, preventing any future instances from starting up, even if the offending empty file is removed.

I think it should just ignore the empty file, offer an option to delete it, etc. 
I have experienced this as well. The only option was to delete the corrupted file and go to the task manager to end the sublime process that was not visibly active.


His solution being implemented would be much appreciated