What's the status on this Windows bug? I've checked github, but can't see a fix.

Development is going on in master branch. I've set github to show release as a default branch instead so anyone can clone github repo and get a stable code instead of my latest dev version that might not work (it points to the latest version released via Package Control).

I will try to make the recent changes cross-platform tomorrow and push 1.30 via Package Control.

1.0.30 is now live on Package Control (as soon as it refreshes itself) and github/release.

Notable changes: - default F2 key bindings has been commented out as they were conflicting with ST2 bookmarks - deleting whole content of REPL buffer broke ruby, this should not happen now - killableprocess is now used instead of subprocess to launch and kill repls. This should fix problems with runaway processes

Aha, so you use a job. I just traverse a tree of child processes and kill them all.

Also tried to send Ctrl+C to a spawned process, so that it passes the signal to the children to make them quit. But apparently you need to do something perverse on Windows in order to send Ctrl+C to a process, since it doesn't work out of the box, and several recipes from google didn't help either. At that point I ignored my initial good intentions and ruthlessly killed child processes.