I’m having an issue using Sublime text 3 on Windows.
I’m using it to edit configuration files for ModTran 5.3.2, an archaic piece of Fortran code that still remains something like the state of the art in it’s field.
When I run ModTran (a command line operation), Sublime Text becomes almost (but not completely) unreponsive (latencies 3-15 seconds, 10 seconds typical) until ModTran is finished.
During it’s run, ModTran loads my i7 processor at about 12%; all other applications remain very responsive, including other editors and file browsers (I can edit the same files with ease using Spyder).
This seems to be tied to Sublime looking through files in directories that are being updated by ModTran. If I open sublime in a different directory, I don’t have this issue. (Note that closing the offending sublime instance is not enough; I have to quit Sublime completely and restart without the offending instance. Once I’ve opened the problematic workspace, the problem persists until I quit again.)
However, closing all files in the output directory, and collapsing the output directory in the toolbar does not fix the problem either.
Any thoughts on causes or solutions?