[Error] Get strange color background thing when integrate Cmder to Windows 10 terminal

[ghost]

I use default settings when intergrate Cmder to Windows 10 Terminal. Both are latest version
Proof
[x]

[chrisant996]

It looks as if a background image may have been configured, as in the background image section of the Windows Terminal documentation.

What happens if a long line of text is typed? Does it extend past the black rectangle into the dimmed image? Is the custom proportional spaced font also affecting the rendering?

[ghost]

Thanks for the reply. I changed every font i got ( even default windows it keeps getting the bug like that). Settings is default.
. My background is fill

[ghost]

If i print long text, it keep this

[chrisant996]

Can you clarify what you're reporting as the issue?

• That a background image is showing up?
• Or that the black background of some lines of text is obscuring the background image?

If the latter, then it sounds like the same as issue #2516. The information there may be helpful to configure the Cmder prompt to avoid the black bars.

[ghost]

Hey there . The method with #2516 you mention is working. Thanks for your help. I will close this comment since fixed :D

[daxgames]

@buinguyenhoangtho did you download the new build and use the new configurable prompt to fix this or did you edit

cmder/vendor/clink.lua

Line 50 in c34eb73

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

[ghost]

@daxgames I'm download the latest and follow the comment :D.

[chrisant996]

@daxgames I'm download the latest and follow the comment :D.

@buinguyenhoangtho Which comment? :)

• The comment about how to modify clink.lua? (Which will get overwritten next time you install an upgrade for Cmder.)
• Or the comment about how to use the latest pre-release build linked in Prompt is printed with SGR 40, resulting in black bands on supporting terminals #2516 and use the brand-new configurable settings? (Which can survive across upgrades of Cmder.)

[ghost]

@buinguyenhoangtho Which comment? :)

• The comment about how to modify clink.lua? (Which will get overwritten next time you install an upgrade for Cmder.)

This one

function my_prompt_filter()
    cwd = clink.get_cwd()
    prompt = "\x1b[1;32;49m{cwd} {git}{hg}{svn} \n\x1b[2;37;49m{lamb} \x1b[0m"
    new_value = string.gsub(prompt, "{cwd}", cwd)
    clink.prompt.value = string.gsub(new_value, "{lamb}", "★")
end

clink.prompt.register_filter(my_prompt_filter, 1)

• Or the comment about how to use the latest pre-release build linked in Prompt is printed with SGR 40, resulting in black bands on supporting terminals #2516 and use the brand-new configurable settings? (Which can survive across upgrades of Cmder.)

Where can i find the latest_pre-release btw? Can you show me the way?

[daxgames]

@buinguyenhoangtho the new code includes a configurable prompt with a settings file in %cmder_root%/config you should be able to set all colors in that and not use a custom prompt filter at all.

[ghost]

@buinguyenhoangtho the new code includes a configurable prompt with a settings file in %cmder_root%/config you should be able to set all colors in that and not use a custom prompt filter at all.

oh ok i get it.

[daxgames]

Latest pre release. https://ci.appveyor.com/project/MartiUK/cmder/build/artifacts

[daxgames]

Please let me know if it works for you.

[ghost]

Ok let me try. I'm usually download it from main website so it old build i afraid?

[ghost]

@daxgames This is prebuild-release and still get the black board

[chrisant996]

@daxgames This is prebuild-release and still get the black board

Did you configure it to use 49? Try that.

[daxgames]

@buinguyenhoangtho there should be a %cmder_root%\config\cmder_prompt_config.lua file you can edit colors in and restart Cmder. The new build does not xhange default settings, it just allows the user to configure them to work with alternate terminals

[ghost]

@buinguyenhoangtho there should be a %cmder_root%\config\cmder_prompt_config.lua file you can edit colors in and restart Cmder. The new build does not xhange default settings, it just allows the user to configure them to work with alternate terminals

so this the result i guess

[daxgames]

I am suprised the entire prompt is green but at least there are no black bars.

[ghost]

I am suprised the entire prompt is green but at least there are no black bars.

yes me too. But one more thing, i can't find anyway to make my VScode terminal after intergrated with Cmder support Emoji. Although Vscode is support Emoji

[ghost]

[chrisant996]

I am suprised the entire prompt is green but at least there are no black bars.

The lamb_color in the screen shot has 30;32m.

32 = green.

It's green because that's what it's been explicitly set to.

[hectormz]

Changing from:

uah_color = "\x1b[1;33;40m" -- Green = uah = [user]@[hostname]
cwd_color = "\x1b[1;32;40m" -- Yellow cwd = Current Working Directory
lamb_color = "\x1b[1;30;40m" -- Light Grey = Lambda Color
clean_color = "\x1b[1;37;40m"

to

uah_color = "\x1b[1;33;49m" -- Green = uah = [user]@[hostname]
cwd_color = "\x1b[1;32;49m" -- Yellow cwd = Current Working Directory
lamb_color = "\x1b[1;30;49m" -- Light Grey = Lambda Color
clean_color = "\x1b[1;37;49m"

got rid of black band and prompt background follows Windows terminal appearance