Child shells yields broken prompt

[NuSkooler]

I have a Python script that sets a bunch of variables, etc., then in turn executes cmd.exe at the end so that I am dropped into a child or "sub" shell with the prepared environment.

When running this cmder, I'm left with a prompt that looks like this:

C:\SomePath {git} 
{lamb}

Any idea on how to fix this? If required, I can change the command in the Python script to be more than just "cmd.exe".

[r3Fuze]

Same thing can happen with npm install.
I looked into it but didn't find a solution.

[samvasko]

Every time you make a new shell thru cmder. It injects the clink to the process. That makes the prompt replacement work. When you run it without that, no replacements happen.

It is not really something you can fix but I am looking into it right now and I might be able to do it smarter.

[NuSkooler]

@Bliker: Do you know of a work around? In my case, I can run something besides simply "cmd.exe" from my script if I know what it should be.

[Jackbennett]

The powershell console does pretty much everything clink injects you could see if running powershell.exe works for you. It's just more strict about running what's in you path not in the directory you happen to be in.

[jankatins]

See #961