microsoft / microsoft/terminal

Exclude Quake window from FancyZones

Open
#10,197 16 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Area-UserInterface Area-Windowing Help Wanted Issue-Bug Issue-Task Priority-3 Product-Terminal
Dominant language
C++
Stars
105k
Forks
9.6k
Avg merge
3d 17h
Merged PRs (30d)
29

Description

# Description of the new feature/enhancement

When I summon quake window while using FancyZones it snaps to the same zone where main terminal window is located.

### Started fresh terminal instance:
![image](https://user-images.githubusercontent.com/38136135/119612712-69eb6000-be26-11eb-8845-8bdd323538b9.png)

### Summoned quake window:
![image](https://user-images.githubusercontent.com/38136135/119612916-ad45ce80-be26-11eb-87b7-8682509da2b1.png)

To solve this problem I can exclude WindowsTerminal.exe from FancyZones, but this way I won't be able to manage regular terminal windows with FancyZones. It would be better if we could exclude only the quake window, but not the other ones.

# Proposed technical implementation details

As I understand, FancyZones uses application executable name for its Exclude rules (might be wrong, tho), thus it could be possible to create a separate executable for quake window, so we could exclude only this one. It's a dirty fix, but it can do the job if there is no other option.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no source files, tests, or entry points; start by reading the FancyZones exclusion behavior and how Windows Terminal identifies its quake window. Done means the quake window can be excluded without preventing regular terminal windows from being managed by FancyZones, with the behavior verified in the relevant window-management tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop, operating-systems
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.