microsoft / microsoft/terminal

always starts on first desktop even when launched from other (sysinternals)

Open
#8,143 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

background/justification: I use sysinternals desktops to isolate some automated tests from my main session. When using Windows 10 virtual desktops, processes which are launched by the automated test run can pop up windows on other desktops which can be a nuisance. Using sysinternals desktops I can run the tests on desktop 2 and their child processes stay there, out of the way of whatever I am looking at on desktop 1.

However... I can't use Windows Terminal to launch those automated tests. If I click on the Windows Terminal button on the taskbar on Desktop 2, Windows Terminal launches on Desktop 1. So I am stuck using ConEmu or ConsoleZ at least for use on desktop 2.

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

Start by reproducing the launch behavior on Windows 10 with Sysinternals Desktops, especially when Windows Terminal is opened from Desktop 2 via the taskbar. Trace how the terminal chooses its desktop during launch. Done means launching it from another desktop opens it there, while child processes remain on that desktop.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.