ConEmu's new "default terminal" feature appears to break flow control if you're using a batch file that is synchronously waiting for a launched cmd window (start /w) to exit

[Maximus5]

Originally reported on Google Code with ID 1859

OS version: Windows 8.1 x64
ConEmu version: 141221

*Bug description*
A build environment I work with uses a batch file that uses "start /w" to launch separate
cmd windows and processes the exit code to continue to the next step. This worked fine
in older versions of ConEmu (it would launch a regular cmd window outside of ConEmu).


This appears to no longer work with the new Default terminal feature.

Repro:

Use the following batch file:

@echo off
echo Step 1... shouldn't proceed to step 2 until the launched window is closed
start /w
echo Step 2... shouldn't proceed to step 3 until the launched window is closed
start /w 
echo Step 3.. done!

If this batch file is run in a regular cmd.exe process, it will stop at each step until
the window is closed. In ConEmu, it launches each window asynchronously and proceeds
immediately.

Reported by goodcool on 2015-01-07 21:17:26

[Maximus5]

Attaching ConEmu.xml (I've stripped out some private information but it should still
represent my configuration)

Reported by goodcool on 2015-01-07 21:22:01

---

- _Attachment: [conemu.xml](https://storage.googleapis.com/google-code-attachments/conemu-maximus5/issue-1859/comment-1/conemu.xml)_

[Maximus5]

One final comment, this issue does not reproduce in 131115.

Reported by goodcool on 2015-01-07 23:38:51

[Maximus5]

You may disable start processing in options.

Reported by ConEmu.Maximus5 on 2015-01-08 01:59:22

---

- _Attachment: 2015-01-08_04-59-25.png
_

[Maximus5]

Perfect. I could have sworn I looked through every option page and didn't see this.
Thank you for such a great tool!

Reported by goodcool on 2015-01-08 18:39:00