I find myself forgetting to focus Sublime after a test run, pretty often, and starting to write code that ends up being written in my terminal instead of Sublime.
After I switch back to Sublime and resume writing my code, I forget to clear out the terminal and start another test run.
Unfortunately, this causes the test run to fail due to the extra crap left on the command line from the previous run.
This turns into a vicious cycle, because I inevitably hit my test-run hot key again, which generates more command line garbage (because the terminal is focused). Lazy developer problems, I guess, but I finally got tired of pulling my hair out over it.
This fix clears out the command buffer before executing the test command.
I find myself forgetting to focus Sublime after a test run, pretty often, and starting to write code that ends up being written in my terminal instead of Sublime.
After I switch back to Sublime and resume writing my code, I forget to clear out the terminal and start another test run.
Unfortunately, this causes the test run to fail due to the extra crap left on the command line from the previous run.
This turns into a vicious cycle, because I inevitably hit my test-run hot key again, which generates more command line garbage (because the terminal is focused). Lazy developer problems, I guess, but I finally got tired of pulling my hair out over it.
This fix clears out the command buffer before executing the test command.