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

[Bug] "Open in Terminal" focuses on last session instead of selected folder #22383

New Issue
Open
opened 2026-01-31 08:11:36 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 08:11:36 +00:00
Owner
Copy Link

Originally created by @Gorrrg on GitHub (Oct 12, 2024).

Windows Terminal version

7.4.5

Windows build number

22631.4317

Other Software

Using Terminal in combination with File Explorer has a certain risk. When you have closed Terminal with open sessions, it will focus on the last session NO MATTER how you have started Terminal again. Literally focusing on a session open in folder A, even though Terminal was started by the user telling it to open a new session in folder X. When you don't know this and start typing your commands right away without checking you might end up destroying your data depending on the operations you do. I happened to me in a hurry. It destroys your workflow. It opens two Terminal windows, one with the old sessions and a new window with the new session you've openend via the Explorer, but for some stupid reason the former gets the focus.

Steps to reproduce

  • Open a few sessions in folders A, B, C.
  • Close Terminal
  • Use File Explorer to "Open in Terminal" folder X
  • There a now two Terminal windows, and focus is on the one with the old sessions instead of the session you have started Terminal again for

Expected Behavior

Open one Terminal window, add the new session to it, and give it focus. Or open two Terimal windows, the old session and in addition a new window with the new session that you actually want to work in, but focus on the latter.

Actual Behavior

Old session steals the focus, you have to manually switch to the session you have just started with "Open in Terminal".

Originally created by @Gorrrg on GitHub (Oct 12, 2024). ### Windows Terminal version 7.4.5 ### Windows build number 22631.4317 ### Other Software Using Terminal in combination with File Explorer has a certain risk. When you have closed Terminal with open sessions, it will focus on the last session NO MATTER how you have started Terminal again. Literally focusing on a session open in folder A, even though Terminal was started by the user telling it to open a new session in folder X. When you don't know this and start typing your commands right away without checking you might end up destroying your data depending on the operations you do. I happened to me in a hurry. It destroys your workflow. It opens two Terminal windows, one with the old sessions and a new window with the new session you've openend via the Explorer, but for some stupid reason the former gets the focus. ### Steps to reproduce - Open a few sessions in folders A, B, C. - Close Terminal - Use File Explorer to "Open in Terminal" folder X - There a now two Terminal windows, and focus is on the one with the old sessions instead of the session you have started Terminal again for ### Expected Behavior Open one Terminal window, add the new session to it, and give it focus. Or open two Terimal windows, the old session and in addition a new window with the new session that you actually want to work in, but focus on the latter. ### Actual Behavior Old session steals the focus, you have to manually switch to the session you have just started with "Open in Terminal".
claunia added the Issue-BugPriority-3Product-TerminalArea-Windowing labels 2026-01-31 08:11:36 +00:00
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-Windowing Issue-Bug Priority-3 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#22383
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?