Closed FelixBoers closed 6 years ago
Hum I don't think you're doing anything wrong, it seems to be a bug on the Package. For what I can see, it's encoding problem.
The package uses os.kill(self.pid, 0)
for UNIX based systems (equivalent to calling kill
on the terminal) but, for Windows, it uses tasklist.exe
. The exception we're seeing seems to be from trying to decode the result of running:
C:\Windows\system32\tasklist.exe /FI PID eq {PROCESS_PID_HERE} /FO CSV
The weird thing is that the decode error is coming from asking the OS the preferred encoding, and trying to decode using that (cp850
in your case).
So!
cross_platform_codecs.py
file located in C:\Users\boers\AppData\Roaming\Sublime Text 3\Packages\Gulp\cross_platform_codecs.py
and changing return text.decode("cp" + chcp)
for
try:
return text.decode("cp" + chcp)
except LookupError:
return text
Hey @NicoSantangelo. Thanks for your help. The problem was that on a german system chcp
returns: Aktive Codepage: 850.\r\n
So after invoking .stripe()
and .split(" ")[-1]
the name of the codepage will be 850.
which is wrong. In order to make it work we've to remove the dot too.
I've submitted a pull request #90
Now everything works fine! Have a nice day
After running
Gulp: Kill running tasks
thenode.exe
process keeps running. AlsoGulp: Kill specific running task
doesn't show anything.I've created an GitHub project with which I can reproduce the problem: https://github.com/flex87/sublime-gulp-kill-watch-task-problem
This is my environment:
This is my gulpfile:
This is what I can read from the console window of Sublime Text after starting the
default
Gulp task:And this is what it shows after running the
Gulp: Kill running tasks
command:Is there something I'm doing wrong?