v2.0.0

[flyingpie]

Introduction

The next major version of Windows-Terminal-Quake, with support for multiple apps simultaneously, including terminals other than Windows Terminal, and apps that are not terminals at all.

Example, with:

• Ctrl + 1: Windows Terminal

• Ctrl + 2: Q-Dir

• Ctrl + 3: Process Hacker

• Ctrl + 4: Spotify

• Ctrl + Q: Most recent app

5ICdmaAYuz.mp4

Current Releases

Portable downloads:
https://github.com/flyingpie/windows-terminal-quake/releases/tag/v2.0.0-pre3

Scoop:
TODO

WinGet:

winget install windows-terminal-quake-prerelease

Plan

The current structure of WTQ (v1.x) has been built entirely on the presumption that there is only ever 1 instance of Windows Terminal. That makes it quite hard to add the ability to handle multiple applications, at the same time.

So I've started on a new application base that is more suited for this expansion, and will add the existing v1 functionality as I go. The new setup can be found under the v2 branch.

Builds

An early build can be downloaded from the releases page.

Note that this build is missing most of the functionality of v1. The initial focus is around converting the app into one that can handle quake-style drop-down on multiple apps, that may or may not be terminal emulators.

Configuration

Although v2 will be backwards compatible with v1 configuration files in the future, it is not yet.

Excerpt from the configuration file that is used with the video above (windows-terminal-quake.jsonc, included in the build):

{
  "Apps": [
    {
      "Name": "Terminal",
      "HotKeys": [ { "Modifiers": "Control", "Key": "1" } ],  // Hotkey specifically for this app.
      "FindExisting": {
        "ProcessName": "WindowsTerminal" // The name of the process to find, note that it's without ".exe".
      }
    },
    {
      "Name": "Spotify",
      "HotKeys": [ { "Modifiers": "Control", "Key": "4" } ],
      "FindExisting": {
        "ProcessName": "Spotify"
      }
    }
  ],
  "HotKeys": [ { "Modifiers": "Control", "Key": "Q" } ] // Hotkey that toggles the most recent app.
}

Current Issues (non-exhaustive)

Missing stuff
V2 is currently missing lots of stuff from v1, while the new basic structure is being put in place to allow for multi-app support.

No auto-start yet
Quake'd applications are currently not started by WTQ v2, they need to be started manually. They can however be exited and re-started, without WTQ needing to restart.

Big boi
The build size (at ~160MB) is ridiculous. I'd like to explore self-contained aot+trimmed CoreCLR builds, but that does require getting rid of the Windows Forms dependency. Said dependency is used for the tray icon and the global hot key functionality.

No tray icon yet (added in pre2)
The current build pops a command prompt, it doesn't drop to the tray yet. I'd like to investigate a different method than v1 used, since that relies on .Net WinForms.

Future Stuff

• Automate different deployments types (GitHub release, Scoop, WinGet, etc.).
  • Some work done on builds, currently outputting zips for self-contained and framework-dependent versions

[fluxium]

Working well so far with https://github.com/alacritty/alacritty/releases/tag/v0.13.1

Super excited for the direction this is going! Thanks @flyingpie!

[flyingpie]

Thank you so much, I'm happy it's of use to you!

Feel free to drop a line if you encounter issues, or have suggestions :)

[flyingpie]

New release available, added tray icon, auto-hide, reduced flickering on some apps, and lots of invisible stuff.
https://github.com/flyingpie/windows-terminal-quake/releases/tag/2.0.0-pre2

[neondeex]

Nice! Does this reduce the q-dir flickering?

[flyingpie]

It does! :)

[flyingpie]

@neondeex Could you confirm or deny whether the flickering has reduced for you?

[neondeex]

@flyingpie Working super good with q-dir
but with notion im having problems that when i open it after some time ti is blank and i have to click to do the rendering

And partially fix the autostar just by having the apps autostart themself

[flyingpie]

We have a prerelease on WinGet now:

winget install windows-terminal-quake-prerelease

The biggest thing missing is an icon in the start menu or something, but small steps!

[flyingpie]

Prerelease 5 available:
https://github.com/flyingpie/windows-terminal-quake/releases/tag/v2.0.0-pre5

This includes initial support for auto-starting apps, which can be done in several ways (see release notes).

[neondeex]

Amazing! update the windget version

[flyingpie]

@neondeex WinGet release is underway for prerelease 6:
microsoft/winget-pkgs#147158
https://github.com/flyingpie/windows-terminal-quake/releases/tag/v2.0.0-pre6

[mateusmedeiros]

Am I correct that the window size is not configurable yet as of the current state of the reworked v2? It's been the only thing missing for me to consider it working perfectly.

Either way, thank you so much for the great work, man! ❤️

[flyingpie]

@mateusmedeiros Thank you for reaching out, and thank you! That is correct, I'll prioritize that as it's small and very useful.

I'll ping you when it's here :)

[flyingpie]

@mateusmedeiros Windows resizing has been added, I'd love to hear if this works for you :)
https://github.com/flyingpie/windows-terminal-quake/releases/tag/v2.0.0-pre6

[mateusmedeiros]

Thanks! I've been busy the last few days with IRL stuff, gonna get back to work around friday and will let you know!

[mateusmedeiros]

@flyingpie I've been testing it for the last 2 hours and it's been working perfectly. I tried a bunch of options with the new 3 settings you added and at first glance it worked exactly as expected.

Coupled with my undecorated wezterm I now have a truly fullscreen terminal that I can open and close with a single keypress. ☺️

Thank you again for all the great work!
❤️

[PiAlma]

Great tool!
I have some remarks (for v2.0.0-prerelease6):

1. Can I use multiple modifiers on the same shortcut ?
2. I would like to remove the windows from the control of wtq become I temporarily want to keep it on screen.
   • Currently: shortcut display the windows. I resized it. The windows lose focus and disappear.
   • What I would like: shortcut display the windows. I resized it (hint for wtq to deactivate its control over this window). The window loose focus, but stay visible until I trigger the shortcut again.
3. If wtq AttachMode is FindOrStart, it will try to start the program, and after a time-out, try again, and again... In my case, I tried the PowerShell from the default wtq.jsonc. But when I launch PowerShell, it is captured by terminal insider. So wtq kept spawning PowerShell. Could you display an error message instead of spawning a new process in case of failure?

Setting to capture PowerShell inside terminal insider:

[flyingpie]

@PiAlma Thank you for your feedback, I really appreciate it! :)

1. You mean like Ctrl+Shift+Q or something?
   If that's the case, yes, I've just written some docs about this here: http://localhost:8000/v2/settings/hotkeys/

TL;DR: List the keys with a comma in between, like:

{
    "HotKeys": [
        { "Modifiers": "Control,Shift", "Key": "W" }
    ]
}

2. I totally get what you're saying, and I'm also in favor of such a feature. The main thing that I'm not quite sure of, is the hint that wtq needs to receive so it knows that it should stop grabbing the app for a bit. I was considering taking a look at the app location, and see if it differs much from where wtq last left it. Do you have any thoughts on this?

3. Interesting one! I did notice that the constant retrying doesn't work great, so it's definitely an area that needs work. A message box to tell you what's going on is very welcome I feel, cause now you're being Jon Snow'ed. I was also wondering about only having the find-or-start process run when wtq starts (like maybe a couple times in the name of retry), then show a message if it fails. Then maybe try again when you actually hit the shortcut.

[PiAlma]

1. It is perfect, that was what I mean.
2. App location is a good idea. You could also add dimension to detect window resizing.

Thank you again for this great tool.

[Heratiki]

I'm not sure what I've done wrong, but I don't believe wtq is working for me at all. If I'm running the Terminal and try and run wtq it just goes back to an empty prompt, and nothing happens. I've attempted installing via winget, winget prerelase, and scoop but still it doesn't do anything. If I run it via the Run Dialog it starts as a background process and just keeps opening new Terminal Windows (none of which are docked). Hoping someone can help.

[flyingpie]

Hey @Heratiki!

I've added some suggestions here: #130

Would you want to take a look and see what happens?

[neondeex]

Is there a way to make transparent every window transparent not only quake?

Also in my portrait screen the quake does not work right

[flyingpie]

@neondeex The patch for the vertical monitor setup is ready, can you take a look here?

https://github.com/flyingpie/windows-terminal-quake/releases/tag/v2.0.10

[neondeex]

Please update the scoop version

[flyingpie]

@neondeex Updated!

[neondeex]

Amazing! All the new updates improved my workflow a loot and now its an amazing app

[flyingpie]

@neondeex Thank you for your feedback! :)

[Bobjeslol]

Hi, I'm loving wtq! I've been trying to get it to work properly with Whatsapp Desktop, but when Whatsapp is in it's 'passive' mode, there's always a white canvas covering the screen. Is this an issue other apps have too? And if so, is there a workaround?

Thanks for your work!

[flyingpie]

@Bobjeslol Thank you for your kind words, and for reaching out! ❤️

Could you post a (crossed out) screenshot of what you're seeing? I'll fire up a Windows machine to test it on my end meanwhile.

[Bobjeslol]

A restart completely changed its behavior. It still isn't doing what I want it to do, though.

Currently the assigned hotkey just opens whatsapp in fullscreen as if i launched the program normally. The swap button doesn't work for whatsapp, it only works for the other apps i have assigned.

This is my whatsapp entry in the settings file:
{ "Name": "Whatsapp", "Hotkeys": [{ "Modifiers": "Control", "Key": "D3" }], "FileName": "C:\\Program Files\\WindowsApps\\5319275A.WhatsAppDesktop_2.2445.7.0_x64__cv1g1gvanyjgm\\WhatsApp.exe", "ProcessName": "WhatsApp" }

I'll try reinstalling whatsapp via the actual executable instead of via the microsoft store, that might make things easier!

[flyingpie]

@Bobjeslol So this seems to have something to do with the sandboxing that's going on with MS Store apps.

I've noticed that they're making it hella hard to do it the "old" way, but let me know if that works!

I'll make an issue for MS Store apps, no promises though, given that the whole point is to keep apps isolated from one another.

[Bobjeslol]

Yeah, that seems to be the issue. Can't get it to work, so I just decided to leave whatsapp out of it. It's time to move to Signal anyways. Thanks for your help!