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

Open terminal on the active screen from windows explorer #17723

New Issue
Open
opened 2026-01-31 05:51:26 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 05:51:26 +00:00
Owner
Copy Link

Originally created by @eMaurits on GitHub (Jun 15, 2022).

Description of the new feature/enhancement

When I right click in a folder and click 'Open in Terminal' it always opens on the main screen while I have the explorer opened on the second or third screen.
Please open the terminal or on the latest screen it was open, or on the screen from where I open the terminal.

Proposed technical implementation details (optional)

Originally created by @eMaurits on GitHub (Jun 15, 2022). # Description of the new feature/enhancement When I right click in a folder and click 'Open in Terminal' it always opens on the main screen while I have the explorer opened on the second or third screen. Please open the terminal or on the latest screen it was open, or on the screen from where I open the terminal. # Proposed technical implementation details (optional)
claunia commented 2026-01-31 05:51:27 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 15, 2022):

Huh. That's not a bad idea. How we communicate where the parent window is might be tricky. I don't know if we can pass in a parent window to ShellExecute, I'd imagine we can. Presumably then CW_USEDEFAULT would respect that. Then, we'd just need a way for --initialPostion (or whatever, #4620) to specify "don't use initialPostion, use CW_USEDEFAULT"

@zadjii-msft commented on GitHub (Jun 15, 2022): Huh. That's not a bad idea. How we communicate where the parent window is might be tricky. I don't know if we can pass in a parent window to ShellExecute, I'd imagine we can. Presumably then CW_USEDEFAULT would respect that. Then, we'd just need a way for `--initialPostion` (or whatever, #4620) to specify "don't use `initialPostion`, use `CW_USEDEFAULT`"
claunia commented 2026-01-31 05:51:28 +00:00
Author
Owner
Copy Link

@smallscript commented on GitHub (Jan 12, 2023):

First, I applaud and support this idea.

Having multiple monitors makes this annoying to not have it.

I frequently use keystrokes to open a terminal from some app (like VsCode) whose window is the keyboard input focus.

The behavior I desire/expect is that the terminal will open up on the same monitor and position itself reasonably in relation to the focused window application from which the launch request was triggered.

As it is now, I can only solve this by moving around the windows setting of my main monitor, or define an AUTO-HOT-KEYS trick to reposition the terminal after it is located ⟨once it is in the foreground⟩.

💯 🤔 🙏

@smallscript commented on GitHub (Jan 12, 2023): First, I applaud and support this idea. Having multiple monitors makes this annoying to not have it. I frequently use keystrokes to open a terminal from some app (like VsCode) whose window is the keyboard input focus. The behavior I desire/expect is that the terminal will open up on the same monitor and position itself reasonably in relation to the focused window application from which the launch request was triggered. As it is now, I can only solve this by moving around the windows setting of my main monitor, or define an AUTO-HOT-KEYS trick to reposition the terminal after it is located ⟨once it is in the foreground⟩. 💯 🤔 🙏
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 Area-ShellExtension Help Wanted Issue-Task 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#17723
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?