starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Allow a command line argument for wt that would accept a monitor designation #20194

New Issue
Open
opened 2026-01-31 07:06:16 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 07:06:16 +00:00
Owner
Copy Link

Originally created by @badgermole on GitHub (Jul 5, 2023).

Description of the new feature/enhancement

I have not found a way to cause a new invocation of wt to position its window onto the monitor of my choice.

Things I have tried:

  1. Manually drag the wt window to my chosen monitor. Close it and start a new wt instance. Other windows respect the Windows settings (System->Display) 'Remember window locations based on monitor connection'. But the wt window does not appear to honor that.
  2. For 'wt --pos <x,y>', set x and y to various values. This works, but only puts the window on the 'main display' monitor.
    Note that for giggles, I tried negative numbers and this caused the window to appear on the other(not main) display monitor, but always at position <0,0>.

Proposed technical implementation details (optional)

Suggestions for possible implementation:
*) Allow another command line arg, perhaps similar to the Linux '--display'.
*) Allow the current <x,y> args of --pos to include an optional monitor number, such as <1:100,100>
*) Honor, the 'Remember window locations based on monitor connection' setting. BUT, allow --pos to override that.

Originally created by @badgermole on GitHub (Jul 5, 2023). # Description of the new feature/enhancement I have not found a way to cause a new invocation of wt to position its window onto the monitor of my choice. Things I have tried: 1) Manually drag the wt window to my chosen monitor. Close it and start a new wt instance. Other windows respect the Windows settings (System->Display) 'Remember window locations based on monitor connection'. But the wt window does not appear to honor that. 2) For 'wt --pos <x,y>', set x and y to various values. This works, but only puts the window on the 'main display' monitor. Note that for giggles, I tried negative numbers and this caused the window to appear on the other(not main) display monitor, but always at position <0,0>. # Proposed technical implementation details (optional) Suggestions for possible implementation: *) Allow another command line arg, perhaps similar to the Linux '--display'. *) Allow the current <x,y> args of --pos to include an optional monitor number, such as <1:100,100> *) Honor, the 'Remember window locations based on monitor connection' setting. BUT, allow --pos to override that.
claunia added the Help WantedIssue-BugProduct-TerminalArea-Commandline labels 2026-01-31 07:06:17 +00:00
claunia commented 2026-01-31 07:06:18 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 12, 2023):

I don't think this needs to be a feature request - this is probably just a bug report 😜 --pos with a negative number absolutely should work! Our psychic debugging guess is that the arg parser we're using is treating --pos -100,-200 as a different option entirely, rather than a value for the --pos arg.

Thanks for finding this!

EDIT: okay it's not that it doesn't accept a negative number, but it does do something weird. I wonder if it's some sort of clipping logic to try and keep the window entirely on the bounds of the display?

@zadjii-msft commented on GitHub (Jul 12, 2023): I don't think this needs to be a feature request - this is probably just a bug report 😜 `--pos` with a negative number absolutely _should_ work! ~Our psychic debugging guess is that the arg parser we're using is treating `--pos -100,-200` as a different option entirely, rather than a value for the `--pos` arg.~ Thanks for finding this! EDIT: okay it's not that it doesn't accept a negative number, but it does do something weird. I wonder if it's some sort of clipping logic to try and keep the window entirely on the bounds of the display?
claunia commented 2026-01-31 07:06:18 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 6, 2023):

Interesting that wt --pos -400,300 seems to snap to the top-left corner of my left display, while "initialPosition": "-400,300" does the right thing. Weird.

@zadjii-msft commented on GitHub (Sep 6, 2023): Interesting that `wt --pos -400,300` seems to snap to the top-left corner of my left display, while `"initialPosition": "-400,300"` does the right thing. Weird.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-Commandline Help Wanted Issue-Bug Product-Terminal
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#20194
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?