Using the application with an sftp source on KDE with KIO can lock up the application when the sftp connection expires, making editing remote a little bit annoying. On KDE applications, it prompts for the key when the connection ends keeping the session active. Would it be possible to at least handle errors when the connection fails (System.IO.IOException: Connection refused) and to revert to a known working path to avoid crashing the application when opening it? Thanks for the great application!
Using the application with an sftp source on KDE with KIO can lock up the application when the sftp connection expires, making editing remote a little bit annoying. On KDE applications, it prompts for the key when the connection ends keeping the session active. Would it be possible to at least handle errors when the connection fails (System.IO.IOException: Connection refused) and to revert to a known working path to avoid crashing the application when opening it? Thanks for the great application!