Odd behavior for Win+R start in Windows 11

[Heratiki]

If you start wtq via the Run dialog (Win+R) in Windows 11 then wtq becomes a background process that will open a new Command Prompt window (not docked like QT) every 5 seconds until you end wtq manually.

I installed wtq via winget. The latest as of this posting date.

[flyingpie]

@Heratiki Thank you for reaching out, I appreciate it!

Could you show me your WTQ config file?

Also, could you show me these settings in WT:

And this in the Windows settings screen:

Finally, if you feel so inclined, could you try a preview build of 2.0.9:
https://github.com/flyingpie/windows-terminal-quake/releases/tag/v2.0.9

Many issues similar to this have already been fixed in that version, I'd love to know whether your particular case is one of them.

[Heratiki]

Give me a few moments to see if I can gather all of that and once I do I'll give 2.0.9 a shot.

It ended up being a few things. For some reason my settings had Windows Console Host setup for my Terminal but the developers setting was set to Let Windows Decide. I think it has to do with Visual Studio 2022 and how it integrates PowerShell for the Dev Environment. Now that I have it all setup as Windows Console Host for both it launches correctly but keeps piggybacking off of the Dev PowerShell so I'm trying to remove those profiles.

So my original issue regarding it creating new terminals every 5 seconds was likely due to Windows choosing the default terminal host.

[Heratiki]

Deleting the Terminal Profiles that were set during Visual Studio 2022 install have helped with making sure the correct shell was being started. So far everything seems to work as intended. I'm still working on finding a good font that works well with Oh My Posh.

[Heratiki]

[flyingpie]

@Heratiki Thank you for your detailed response!

This whole thing is definitely an area that needs to become smoother.

The core of the problem here boils down to not knowing whether Windows Terminal is present or not. And on top of that, whether we can just spawn command prompts without them being captured by WT.

Since you are using it with WT, you could switch the configuration to use WT directly:

{
  "Apps": [
    {
      "Name":         "Terminal",
      "HotKeys":      [{ "Modifiers": "Control", "Key": "D1" }],
      "FileName":     "wt",
      "ProcessName":  "WindowsTerminal"
    }
  ]
}

That would make the configuration less dependent on whether or not WT is set as the default console host.

Aside from the proces of getting there certainly not being perfect, is everything working for you now?

[Heratiki]

I use PowerShell rather than WindowsTerminal. So I'm running pwsh and things tend to work really nice now without much issue.

[flyingpie]

@Heratiki Ah, so you don't even actually run WT at all, not even as a console host?

Would you care to show a screenshot of the running situation?