Closed devjones closed 5 years ago
I am suffering from the same issue. Have you found a fix?
I have one in my head, but not quite time right now to implement it. Right now I rely on Sublime Text's capabilities to run commands, but it would probably be more robust to use Popen to spawn the process and keep control of it, tearing it and all the child processes down properly on "kill". However, as I said, this is not a priority for me right now.
Any help will be greatly appreciated!
For anyone trying to figure out how to kill live reload task, type curl localhost:25710/kill replacing the numbers with your own.
Repository was moved to https://github.com/sptndc/sublime-grunt Please re-file any issues that still exist.
I have a grunt task (grunt watch) which uses LiveReload. LiveReload uses port 35729 to communicate with the browser.
I'm noticing that when I use the grunt kill command with this plugin that port 35729 remains open. It should be closed along with any other tasks initiated by grunt.
When I do a hard kill from the command line using Ctrl-C, port 35729 is successfully closed.