Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Intensity Effect Not Applied for Escape 38 #11507

Closed
mkernalcon opened this issue Oct 14, 2021 · 4 comments
Closed

Intensity Effect Not Applied for Escape 38 #11507

mkernalcon opened this issue Oct 14, 2021 · 4 comments
Labels
Product-Terminal The new Windows Terminal. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@mkernalcon
Copy link

Windows Terminal version (or Windows build number)

1.10.2714.0

Other Software

No response

Steps to reproduce

(in bash): echo -e "\033[01;34mBright \033[00m \033[1;38;5;4mShould be\033[00m"

Expected Behavior

Both come out blue, with your selected intensity effect from "intenseTextStyle", similar to Putty, iTerm, etc.

Actual Behavior

The intensity effect is only applied in the first case ("Bright"), and not in the second ("Should Be")

@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Oct 14, 2021
@zadjii-msft
Copy link
Member

Can you share your settings.json?

@zadjii-msft zadjii-msft added Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something Product-Terminal The new Windows Terminal. labels Oct 14, 2021
@mkernalcon
Copy link
Author

settings.json

@ghost ghost added Needs-Attention The core contributors need to come back around and look at this ASAP. and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels Oct 14, 2021
@DHowett
Copy link
Member

DHowett commented Oct 14, 2021

Thanks for the report! This was an intentional decision, based on how other terminal emulators work. I went and dug up some of our older discussions to give you more context. 😄

Here's the short version:

I'll tentatively close this one out as a /duplicate of #5384 😄

@ghost
Copy link

ghost commented Oct 14, 2021

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed Oct 14, 2021
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements Needs-Attention The core contributors need to come back around and look at this ASAP. labels Oct 14, 2021
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Product-Terminal The new Windows Terminal. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

3 participants