Error message is unnecessarily escaped

[kfir-drivenets]

I try to run a local script awesome_script.py param1 param2 the error I got was awesome\_script.py command not found. Note that added \ to the command name. When I run the same script directly with my shell, e.g /bin/sh -c awesome_script.py param1 param2 everything works like a charm..

[kfir-drivenets]

Turns out the issue was locally on my end, needed to add -i flag to shellArgs and all worked.

[ryu1kn]

Hi @kfir-drivenets , thanks for updating us with the conclusion. I was away on holiday.

I try to run a local script awesome_script.py param1 param2 the error I got was awesome\_script.py command not found. Note that added \ to the command name.

The \ seems to be coming from this text escaping rule, which is only apply to error messages. So I guess what happened was, the shell did look for awesome_script.py but couldn't find one and generated an error message, awesome_script.py command not found, which then the extension added \ just before it showed you the message.

The error message should have been awesome_script.py command not found. Looking at this test case about the formatting, I shouldn't escape single _ but double underscores __.

[ryu1kn]

I repurpose this issue 😉 I've updated the issue title.