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

defaultProfile setting is no longer respected #5489

Closed
zawor opened this issue Apr 23, 2020 · 6 comments
Closed

defaultProfile setting is no longer respected #5489

zawor opened this issue Apr 23, 2020 · 6 comments
Labels
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

Comments

@zawor
Copy link

zawor commented Apr 23, 2020

It seems like after upgrading to 0.11.1121.0 defaultProfile setting is no longer respected.

Environment

Windows build number: Microsoft Windows NT 10.0.19041.0
Windows Terminal version (if applicable): 0.11.1121.0

Any other software?
plenty but probably irrelevant ;)

Steps to reproduce

  1. Have a multiple profiles configured where powershell.exe is not default.
  2. Start Windows terminal
  3. You start always with powershell.exe one

alternatively
2. ctrl +alt + - causes always to load powershell.exe one regardless which one currently is active

Expected behavior

defaultProfile gets loaded on startup

Actual behavior

defaultProfile is ignored

I attach settings file for reference:
settings.zip

PS:
If you need more details simply let me know.

@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 Apr 23, 2020
@mlewand
Copy link

mlewand commented Apr 23, 2020

You need to move all your settings from global key (in your settings.json) outside of global key (to the root level).

Duplicate of #5458.

@zawor
Copy link
Author

zawor commented Apr 23, 2020

this solves my problem... but damn... visibility of this breaking change is close to none if you are not tracking terminal changes eagerly...

Anyway thank you for resolving my issue! :)

@zawor zawor closed this as completed Apr 23, 2020
@mlewand
Copy link

mlewand commented Apr 23, 2020

@zawor agree, I also missed it myself, despite "reading" (or scanning, I should say) the changelog (#5458 (comment)) 😄

@mdtauk
Copy link

mdtauk commented Apr 23, 2020

I was trying to update my settings to set the theme, and I was trying to put the entry in the defaults section, wondering why it wasn't working - until I moved it to root.

It feels quite odd using the JSON root for elements, but I guess once the Settings UI is added, it will become redundant to think too much about it. :)

@zawor
Copy link
Author

zawor commented Apr 23, 2020

@mlewand mine was even worse... i run on windows store version, so today out of sudden i got caught with my pants down by this regression :P

personally i would love to have (opt in) possibility to get smacked in the face with release notes dialog/tab/view/whatever every time i get auto updated, lets say just like in VS Code

@mlewand
Copy link

mlewand commented Apr 23, 2020

@zawor Sounds like a good feature request 🙂 what I'm doing is I subscribed to release-only on GH so that I get notification about the release, check the changelog and then upgrade it using chocolatey (decent package manager, so the upgrade is as simple as typing cup microsoft-windows-terminal /y once I'm sure I want to upgrade).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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
Projects
None yet
Development

No branches or pull requests

3 participants