Currently, the application will silently fail and leave no trace of an error in a log file if there's an unhandled exception. We should perhaps add some quick way to resolve it, because now we have no way of determining why editor has crashed for someone unless they're running the editor from opened terminal session. Adding our own callback to AppDomain.CurrentDomain.UnhandledException will maybe be enough?
Currently, the application will silently fail and leave no trace of an error in a log file if there's an unhandled exception. We should perhaps add some quick way to resolve it, because now we have no way of determining why editor has crashed for someone unless they're running the editor from opened terminal session. Adding our own callback to
AppDomain.CurrentDomain.UnhandledExceptionwill maybe be enough?