vim-ruby-conque icon indicating copy to clipboard operation
vim-ruby-conque copied to clipboard

Conqueterm instances are not closed, leaving zombie ruby process

Open skwp opened this issue 12 years ago • 0 comments

When you close a buffer running a (completed) conque, the ruby process hangs around, eating up a tty (causing 'unable to fork' errors in iterm), and other problems. Need to figure out how to nuke the ruby process once it's finished running. This is not a problem when you run a regular rspec command yet conque makes it hang around for some reason.

skwp avatar May 18 '13 17:05 skwp