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

Disable use of bright colors for bold text #3613

Closed
maggu opened this issue Nov 18, 2019 · 3 comments
Closed

Disable use of bright colors for bold text #3613

maggu opened this issue Nov 18, 2019 · 3 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@maggu
Copy link

maggu commented Nov 18, 2019

Description of the new feature/enhancement

The OS X Terminal has a setting for “Use bright colors for bold text”. If it is disabled I always get normal colors for bold text, which I have found to be quite useful for readability on a terminal with bright background (which I personally prefer).

I can of course change the color scheme, which solves the issue locally. However, when I connect to a Linux server with ssh, it has a color scheme of its own. (Which I can also change, but it would be more practical if the terminal were able to handle it.)

Perhaps some time after Windows Terminal is able to display actual bold text?

@maggu maggu added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Nov 18, 2019
@ghost ghost added Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Nov 18, 2019
@egmontkob
Copy link

#include "#2916"

@DHowett-MSFT
Copy link
Contributor

@egmontkob thanks for connecting these up! This is, more correctly, a /dupe of #109 (although right now it points at the wrong product 😄)

@ghost
Copy link

ghost commented Nov 18, 2019

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 Nov 18, 2019
@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 labels Nov 18, 2019
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. 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