Gitextensions: 2.50.00/2.50.01 introduced issue parsing " in scripts

[XopherThomas]

Do you want to request a feature or report a bug?
Bug Report:

What is the current behavior?
Previous to Git Extension 2.50.00, I was using a scripts feature to run a bash script. This bash script is designed to allow for Right Click deletion of remote branches. Upon updating to Git Extensions 2.50.00 and 2.50.01, this feature is now broken and reports an error.
My scripts command is:
Name: Delete Remote Branch
Add to revision grid context menu: Checked
Command: bash
Arguments: -c "git push origin --delete $(echo {sRemoteBranch} | sed 's/origin\///')"

in order to take the currently selected remote branch, strip the "origin/" from the branch name and delete it from the server.

After 2.50.00 I get the following error instead reporting a failure to parse the ending "
"bash" -c "git push origin --delete $(echo origin/personal/thomasc/prototype_acl-17784 | sed 's/origin\///')" /usr/bin/bash: -c: line 0: unexpected EOF while looking for matching `"' /usr/bin/bash: -c: line 1: syntax error: unexpected end of file Done

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.
Additionally, I tried a more simplistic example and get the same result parsing the ending ":
Name: Test command
Add to revision grid context menu: Checked
Command: bash
Arguments: -c "git --version"
also results in
"bash" -c "git --version" /usr/bin/bash: -c: line 0: unexpected EOF while looking for matching `"' /usr/bin/bash: -c: line 1: syntax error: unexpected end of file Done

Additionally, I tried running just a bash command which seems to run properly:
Name: Test command 2
Add to revision grid context menu: Checked
Command: bash
Arguments: "--version"

and reports as expected:
````
GNU bash, version 4.4.12(1)-release (x86_64-pc-msys)
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html

This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
````
What is the expected behavior?
for it to properly parse the passed input and execute the command

Which versions of GitExtensions, GIT and Windows are affected by this issue? Did this work in previous versions of our tool?
Versions
Windows 7
Git Extension 2.50.00/2.50.01
Git 2.13.2.windows.1
Yes, this worked previously prior to 2.50.00

[vbjay]

Please use the issue template next time.

[RussKie]

Thank you for the submission.
Next time please format commands and outputs with ` and ``` (https://guides.github.com/features/mastering-markdown/), it makes it easier to read.

[pmiossec]

It seems to be again a problem with Conemu.
Could you try to disable it and tell us if it fix your problem?
Follow this doc to find the setting to do so:

https://git-extensions-documentation.readthedocs.io/en/latest/settings.html#advanced-general-use-console-emulator-for-console-output-in-command-dialogs

[XopherThomas]

Thank you pmiossec. By disabling Console Emulator, I was able to perform the command as expected. This is a great workaround.

[jbialobr]

As a fix I suggest to always run scripts in the standard GitExtensions status dialog regardless of Console Emulator being enabled.