{lamb} instead of lambda sign (possibly a UTF-8 problem?)

[jszym]

Instead of getting a pretty lambda sign, I get {lamb} as my prompt. 😞

[MartiUK]

Do you have clink installed already?

[jszym]

yup :)

[MartiUK]

The clink you have installed is conflicting with clink that's included with the full install.

You have two options:

Uninstall clink and use cmder as is.

Or
(I don't know if this will work)

Remove the clink directory from the vendor folder and adjust this line in init.bat:
https://github.com/bliker/cmder/blob/master/vendor/init.bat#L22

to something like:

:: Run clink
@"clink_x%architecture%.exe" inject --quiet --profile "%CMDER_ROOT%\config"

If clink is in your PATH already.

[Marsup]

I have the same bug. Removed your installation of clink and created a symlink to mine instead, it didn't solve the problem. Anything else I can try ?

[Marsup]

Well, uninstalling was the key. I had the copyright of clink when running cmder so I thought it launched twice. I don't think it's possible to keep both.

[tengwar]

I have the same problem when running Cmder as root, but everything is fine when I run it as me. In a root tab I get a warning that translates to

System can't find the given path.
File not found - C:\Users\User\Copy\random\config\aliases

I have it in a directory like "C:\Users\User\Copy\random stuff", so it looks like spaces aren't handled properly in root mode.

[K900]

Same issue on Windows 10 Technical Preview is solved by upgrading to Clink 0.4.3

[CoreyH]

Windows 10 RTM I am having this issue. I installed/upgraded to Clink 0.4.3 via Chocolatey and I am still stuck with {lamb}

[ClementParis016]

Same problem for me on latest Windows 10, I have no other Clink installed next to the one included with Cmder

[flyingduck92]

any solution?

[MartiUK]

Download the latest pre-release, do not install anything from chocolatey.

[jasonwilliams]

i downloaded the latest version of clink and still have this issue
(using 1.2.9)

[MartiUK]

Clink is included with cmder already.

[kowsheek]

The latest prerelease didn't fix the issue.

[bittin]

yeah got that problem in Windows 10 on my work computer like 2 days ago aswell, when opening up a new cmd.exe :(

[jasonwilliams]

@MartiUK people still having issues, maybe this should be re-opened?

[flyingduck92]

i fix the issue by uninstall clink on my PC before i use cmder

[kowsheek]

I fixed it by installing a updated version to the clink folder in cmder.

[jasonwilliams]

I also did the above to fix it, the pre-release didn't solve it for me