jerrytaffy / conque

Automatically exported from code.google.com/p/conque
0 stars 0 forks source link

destroying a buffer doesn't terminate conqueterm hosted process #50

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. ConqueTermSplit bash --restricted
2. ps aux | grep bash
   Confirm there is exactly one bash with the --restricted commandline option
2. <ESC>:bd
3. :ls
   Note that the buffer is no longer listed in vim
In another terminal:
4. ps aux | grep bash
   Notice the 'bash --restricted' process is still running?
5. Exit vim.
6. ps aux | grep bash
   Notice the 'bash --restricted' process has been killed.

What is the expected output? What do you see instead?
In step 4 I would expect the bash process to have been killed as the terminal 
window controlling it is no longer accessible.

What version of the product are you using? On what operating system?
ConqueTerm 2.1, Vim 7.3, Ubuntu 10.10

Please provide any additional information below.
I can't think of any.

Original issue reported on code.google.com by bobp...@gmail.com on 15 Apr 2011 at 10:39

GoogleCodeExporter commented 8 years ago
Resolved in trunk

Original comment by nicora...@gmail.com on 15 Aug 2011 at 8:41