Cmder: Cmder lambda and info virtualenv not appearing or the color is wrong

Created on 29 Oct 2017  ·  17Comments  ·  Source: cmderdev/cmder

Lambda character, not appearing. I believe the color is the same background, but I could not change.
cmder version 1.3.3
OS: Windows 10 Fall Creators Version 1709 build 16299.19

1
2
3
4

Thanks in advance
Sorry for my English

Most helpful comment

@rhpijnacker I resolved this problem just open C:\cmder\vendor\clink.lua file with my editor, then located to 41 line and replace 30 with 39. Just like:

Old: local cmder_prompt = "\x1b[1;32;40m{cwd} {git}{hg}{svn} \n\x1b[1;30;40m{lamb} \x1b[0m"
New: local cmder_prompt = "\x1b[1;32;40m{cwd} {git}{hg}{svn} \n\x1b[1;39;40m{lamb} \x1b[0m"

refer to : a8d3261

All 17 comments

It worked !!! Thanks.

In Contingency, I had downloaded the conemu portable and replaces the original conemu of the version 1.3.3, but is now solved. ;-)

Just need to update the builds.

Closed

@Stanzilla

I preferred to replace ConEmu portable, the color of the text λ and venv are in gray. I think this is the cmder default.

I'm practically out of time so I could not pinpoint what the problem was. I did some testing here and when I replaced the files
conemu-maximus5 \ ConEmu \ ConEmuHk64.dll
conemu-maximus5 \ ConEmu64.exe

ConEmu updated and fixed the problem.

I am not familiar with the project, but perhaps re-packaging with the current version of ConEmu could solve the problem.

Follow the print with powerline installed ;-)

1

@adautoserpa So which version of ConEmu did you download and install? Because 1.3.3 actually comes with the latest alpha version. So if you downloaded the latest release version, you actually downgraded ConEmu and only delayed running into the problem

@Stanzilla I am using the stable version 161 206.
I downloaded alpha version 171025 and did the same procedure. The bug appears.
This leads to believe that it is some bug in the conemu or some incompatibility with the alpha version.

Yup makes sense, thank you for checking!

@maximus5 Intended change or regression?

To set highlighted foreground colors it's recommended to use ESC [ 90..97 m instead of ambiguous BrightOrBold.
Intended change.

@Stanzilla and @Maximus5
We could use the code below to have the same result as the previous version of cmder, dark gray.

local cmder_prompt = "\x1b[1;32;40m{cwd} {git}{hg}{svn} \n\x1b[1;30;90m{lamb} \x1b[0m"
or
local cmder_prompt = "\x1b[1;32;40m{cwd} {git}{hg}{svn} \n\x1b[30;90m{lamb} \x1b[0m"

ESC [ 30..90 m

@vbm suggested using 39m because that's the default color of foreground at startup -> https://github.com/shiena/ansicolor/blob/master/README.md
I'm inclined to leave it like that.

I use this:

local cmder_prompt = "\x1b[1;32;40m{cwd} {git}{hg}{svn} \n\x1b[1;37;40m{lamb} \x1b[0m"

then the color is the same as code,i like it. nice.

Just to let you know: Just downloaded the minimal version from the cmder home page (v1.3.3/cmder_mini.zip) and ran into the same issue.
Not really sure what the right fix is, after reading the conversation.

@rhpijnacker I resolved this problem just open C:\cmder\vendor\clink.lua file with my editor, then located to 41 line and replace 30 with 39. Just like:

Old: local cmder_prompt = "\x1b[1;32;40m{cwd} {git}{hg}{svn} \n\x1b[1;30;40m{lamb} \x1b[0m"
New: local cmder_prompt = "\x1b[1;32;40m{cwd} {git}{hg}{svn} \n\x1b[1;39;40m{lamb} \x1b[0m"

refer to : a8d3261

@Stanzilla Can I close the issue?
Then tell us when to leave the build with the fix. Thank you!

I think so, yeah. 1.3.4 is out now

@Stanzilla the official cmder download link leads to version 1.3.3.

@freiro I know, the PR updating the links has not been merged yet.

@Stanzilla #worked like a charm 👍 👍 👍

Was this page helpful?
0 / 5 - 0 ratings

Related issues

hyrious picture hyrious  ·  3Comments

jenisys picture jenisys  ·  3Comments

giuliannosbrugnera picture giuliannosbrugnera  ·  3Comments

Joe1992w picture Joe1992w  ·  3Comments

luisrudge picture luisrudge  ·  3Comments