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

Retain font-size and opacity changes made in terminal window #4855

Closed
abhijeetviswam opened this issue Mar 9, 2020 · 3 comments
Closed

Retain font-size and opacity changes made in terminal window #4855

abhijeetviswam opened this issue Mar 9, 2020 · 3 comments
Labels
Area-Settings Issues related to settings and customizability, for console or terminal Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Product-Terminal The new Windows Terminal. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@abhijeetviswam
Copy link
Contributor

Description of the new feature/enhancement

Any changes to font-size and acrylic opacity done from the terminal window using ctrl/shift hotkeys+mouse scroll gesture need to be made persistent.

In the existing implementation, any changes in font size or opacity made while using the terminal window and not explicitly changed in profile.json is not being retained. I think it would be more user friendly if the user preferences are retained without explicit change in settings.

@abhijeetviswam abhijeetviswam added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Mar 9, 2020
@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 Mar 9, 2020
@zadjii-msft
Copy link
Member

This is pretty close to the following discussions:

#766
#1056
#961

Though, none of them call out specifically persisting window state like this automatically. I'm wondering if there's one that this should be merged in with, or if we should leave this open as it's own unique discussion 🤔

@zadjii-msft zadjii-msft added the Area-Settings Issues related to settings and customizability, for console or terminal label Mar 23, 2020
@zadjii-msft zadjii-msft added the Product-Terminal The new Windows Terminal. label Mar 23, 2020
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Mar 23, 2020
@zadjii-msft zadjii-msft added this to the Terminal Backlog milestone Mar 23, 2020
@DHowett-MSFT
Copy link
Contributor

I think this is best considered a feature of /dup #1056, honestly. Being able to take the "current active" settings and positively confirm committing them somewhere would really seal the deal.

@ghost
Copy link

ghost commented Mar 27, 2020

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 Mar 27, 2020
@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 labels Mar 27, 2020
@zadjii-msft zadjii-msft removed this from the Terminal Backlog milestone Jan 19, 2021
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Settings Issues related to settings and customizability, for console or terminal Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. 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