Starting Windows Terminal with Win+X should lead to a different default profile #13284

Activity

1. Charlotte (csdvrx)

   added

   Issue-BugIt either shouldn't be doing this or needs an investigation.It either shouldn't be doing this or needs an investigation.

   on Jun 12, 2022
2. ghost added

   Needs-Tag-FixDoesn't match tag requirementsDoesn't match tag requirements

   on Jun 12, 2022
3. ghost added

   Needs-TriageIt's a new issue that the core contributor team needs to triage at the next triage meetingIt's a new issue that the core contributor team needs to triage at the next triage meeting

   on Jun 12, 2022
4. zadjii-msft commented on Jun 13, 2022

   

   Mike Griese (zadjii-msft)

   on Jun 13, 2022

   Member

   More actions

   Hmm. There's a lot to unpack here.

   • I'm pretty confident that there's no way for us to identify that we were launched via the Win+X menu. They're basically just calling wt.exe, if they can tell that we're installed.
   • THEORETICALLY, you could change those shortcuts yourself. There is a way to manually change the entries in the win+X menu, and you could totally change that to wt -p <whatever>.
   • There is already a request for "global summon a window with a specific profile" (somewhere between Quake mode: Add support for reserved tabs #10279 and Summon window and switch to profile #12135). Then you could always bind something like, Win+Shift+X to summon --profile "Command Prompt", or whatever.
   • There's also Add per-window-name global settings #9992, for "change the defaultProfile of the _quake window
5. Mike Griese (zadjii-msft)

   added

   Issue-QuestionFor questions or discussionFor questions or discussion

   Product-TerminalThe new Windows Terminal.The new Windows Terminal.

   and removed

   Issue-BugIt either shouldn't be doing this or needs an investigation.It either shouldn't be doing this or needs an investigation.

   on Jun 13, 2022
6. Mike Griese (zadjii-msft)

   added this to the Backlog milestone on Aug 9, 2023
7. Mike Griese (zadjii-msft)

   added

   Issue-FeatureComplex enough to require an in depth planning process and actual budgeted, scheduled work.Complex enough to require an in depth planning process and actual budgeted, scheduled work.

   and removed

   Issue-QuestionFor questions or discussionFor questions or discussion

   Needs-TriageIt's a new issue that the core contributor team needs to triage at the next triage meetingIt's a new issue that the core contributor team needs to triage at the next triage meeting

   on Aug 9, 2023
8. zadjii-msft commented on Aug 9, 2023

   

   Mike Griese (zadjii-msft)

   on Aug 9, 2023

   Member

   More actions

   Okay, we discussed more as a team today.

   The way things are today, this is probably unsolvable without a lot of platform support.

   We discussed a theoretical solution:

   • First, we need to fix the COM elevation thing, so that running an elevated CLI exe can possibly activate a defterm application. (which is tracked in.... some thread that needs finding)
   • Then, we could just revert the platform-side changes that made the Win+X menu point at wt.exe. Point it back at your choice of cmd.exe or powershell!
   • Then, the shortcuts will store properties in the .lnk again, like they used to.
   • Then, some work that's linked to Epic: Default-by-default fall-out, long-term plans, and community feedback #13392 should let us get some settings from the lnk. So that will feel like different profiles, or we could explicitly make different profiles for different .lnks for defterm.

   But that's probably years out.