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

Cursor color should be part of color scheme, not profile #3322

Closed
cayv opened this issue Oct 25, 2019 · 3 comments
Closed

Cursor color should be part of color scheme, not profile #3322

cayv opened this issue Oct 25, 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

@cayv
Copy link

cayv commented Oct 25, 2019

Changes

I wrote a small script to import Terminal color schemes from VSCode themes. However, there's something I think is unintended design:

The "cursorColor" setting is currently part of the profile, not the color scheme. In my opinion it doesn't make sense, because by changing the color scheme of a given profile, the background color may be similar to the cursor color. Both settings should be coupled to each other for consistency.

Additional features

It'd be amazing if you guys could implement the few remaining color customization options from VSCode's terminal to reach feature parity. They are:

  • terminal.border: The color of the border that separates split panes within the terminal.
  • terminal.selectionBackground: The selection background color of the terminal.
  • terminalCursor.background: The background color of the terminal cursor. Allows customizing the color of a character overlapped by a block cursor.
@cayv cayv added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Oct 25, 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 Oct 25, 2019
@zadjii-msft
Copy link
Member

zadjii-msft commented Oct 25, 2019

Thanks for the report. I believe we have issues for a lot of these already, so lemme link them up:

In general, it's really hard for us to track and resolve issues that have a bunch of suggestions in them. I'm going to move selection BG color to it's own issue, cursor bg/fg into #1203, and I'll make an issue for "theming" that will incorporate the pane border BG color.

Thanks for the feedback!

@zadjii-msft
Copy link
Member

/dup #764
/dup #3327
/dup #3326
/dup #1203

@ghost
Copy link

ghost commented Oct 25, 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 Oct 25, 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 Oct 25, 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

2 participants