Extra stuff in command line?

[GoogleCodeExporter]

The command line "cmd /k start cmd /k cd /d ..." seems too complex. Why do
you need the extra command processor? Wouldn't just "cmd /k cd /d ..." be
sufficient?

What steps will reproduce the problem?
1. Right-click on a resource and choose "Open in Command Prompt"
2. Note that two cmd.exe processes are created:
  eclipse
    |- cmd.exe
        |- cmd.exe

Also, after closing the resultant command window, the parent cmd.exe hangs
around.

What is the expected output? What do you see instead?
Only one child cmd.exe expected. No cmd.exe processes expected after
closing the command window.

What version of the product are you using? On what operating system?
1.2.1 on Windows XP

Please provide any additional information below.

Original issue reported on code.google.com by dcit...@gmail.com on 25 Aug 2008 at 8:36

[GoogleCodeExporter]

>Wouldn't just "cmd /k cd /d ..." be
sufficient?
1. No it wouldn't. You can try it yourself...
2. I'm not that expert in batch scripting, but as I understand it you need 
shell in
order to invoke 'start' command. And you need 'start' in order to display a new
window. And then you need another shell to execute the 'cd' command.

So the first shell is used to run the 'start' and the second shell is going to 
be
displayed.

However, I do see a problem here, since the first shell is not going to be 
closed,
when the second shell is closed.

I have added a bit of ugly fix for this problem: I terminate the original 
process
after 500 milliseconds delay, just to make sure that all processes were started
correctly.

Original comment by tarlog on 26 Aug 2008 at 5:03

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by tarlog on 26 Aug 2008 at 6:44

[GoogleCodeExporter]

Original comment by tarlog on 13 Sep 2009 at 5:44

• Changed state: Verified