Cmder prompt screwed up with latest Windows 10 Build

[ultralisk-]

Windows 10 Preview Build 14251
Cmder Version: 1.2.9

See this screenshot

I have multiple machines running Windows 10, both experienced this problem after installing the latest insider preview. I suspect Microsoft have broken something as I've noticed a few other bugs.

[amoshydra]

I face this problem after upgrading to Build 14251 too.
Is it fine to apply this workaround until the problem is fixed?

in vendor/init.bat change
@prompt $E[1;32;40m$P$S{git}{hg}$S$_$E[1;30;40m{lamb}$S$E[0m
to
@prompt $P$S$_{lamb}

*Edited to include $P$S file path

[MartiUK]

I can't reproduce this as I am not using the insider builds, could you report it to the clink repository?

[ultralisk-]

Done: mridgers/clink#377

[yangbohz]

I have the same problem. It can be fixed by a reset. But cmder will have other weird problem.