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

"Open in Terminal" context menu item does not open terminal in that location #18407

New Issue
Closed
opened 2026-01-31 06:13:01 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 06:13:01 +00:00
Owner
Copy Link

Originally created by @eggbean on GitHub (Sep 9, 2022).

I have WSL2 (Pengwin) set as the default shell in Windows Terminal. The problem is that the "Open in Terminal" right-click context menu does not open WSL at that location. It always open at $HOME whatever the case.

Windows Terminal settings:

# Under Startup
Default profile: Pengwin
Default terminal application: Let Windows decide
When Terminal starts: Open a tab with the default profile
Launch mode: Default
New instance behaviour: Create a new window
# Under Pengwin
Command line: %ProgramFiles%\WindowsApps\WhitewaterFoundryLtd.Co.16571368D6CFF_22.3.2.0_x64__kd1vv0z0vy70w\DistroLauncher\pengwin.exe
Starting directory: blank
     Use parent process directory - ticked

I don't know what else could be relevant, but here is my entire settings.json.

Is it actually possible for WSL2 to open in file system locations using this context menu item or does it only work with cmd.exe?

At the moment I keep Alacritty installed just so that I can use its context menu item to open it at specific locations.

Originally created by @eggbean on GitHub (Sep 9, 2022). I have WSL2 (Pengwin) set as the default shell in Windows Terminal. The problem is that the "Open in Terminal" right-click context menu does not open WSL at that location. It always open at `$HOME` whatever the case. Windows Terminal settings: ``` # Under Startup Default profile: Pengwin Default terminal application: Let Windows decide When Terminal starts: Open a tab with the default profile Launch mode: Default New instance behaviour: Create a new window # Under Pengwin Command line: %ProgramFiles%\WindowsApps\WhitewaterFoundryLtd.Co.16571368D6CFF_22.3.2.0_x64__kd1vv0z0vy70w\DistroLauncher\pengwin.exe Starting directory: blank Use parent process directory - ticked ``` I don't know what else could be relevant, [but here is my entire settings.json](http://sprunge.us/NWknNo). Is it actually possible for WSL2 to open in file system locations using this context menu item or does it only work with cmd.exe? At the moment I keep Alacritty installed just so that I can use its context menu item to open it at specific locations.
claunia added the Needs-TriageNeeds-Tag-FixNeeds-Attention labels 2026-01-31 06:13:01 +00:00
claunia commented 2026-01-31 06:13:03 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 9, 2022):

Ah, this is the same root cause as the Ubuntu startingDirectory bug. Pengwin has included a JSON file that overrides the commandline to point to pengwin.exe, but pengwin.exe does not respect the starting directory. Any executable that ignores its working directory will exhibit this behavior.

The best option is to let them know; this will break starting directory inheritance for any invocation of pengwin inside or outside of Terminal[1].

The second best option is to set the commandline back to wsl -d Pengwin (or whatever it's actually called when you run wsl -l)

[1] you can see this if you run, from cmd, cd c:\users & pengwin.

@DHowett commented on GitHub (Sep 9, 2022): Ah, this is the same root cause as the Ubuntu `startingDirectory` bug. Pengwin has included a JSON file that overrides the commandline to point to `pengwin.exe`, but `pengwin.exe` _does not respect the starting directory._ Any executable that ignores its working directory will exhibit this behavior. The best option is to let them know; this will break starting directory inheritance for any invocation of `pengwin` inside or outside of Terminal[1]. The second best option is to set the commandline back to `wsl -d Pengwin` (or whatever it's actually called when you run `wsl -l`) [1] you can see this if you run, from cmd, `cd c:\users & pengwin`.
claunia commented 2026-01-31 06:13:03 +00:00
Author
Owner
Copy Link

@eggbean commented on GitHub (Sep 9, 2022):

In Windows Terminal settings I have changed Command line: to wsl -d WLinux (which is the original name for Pengwin) and I changed Starting directory: to ~ and it's doing exactly what. I'll mention it in their Issues. Thanks for your help.

@eggbean commented on GitHub (Sep 9, 2022): In Windows Terminal settings I have changed `Command line:` to `wsl -d WLinux` (which is the original name for Pengwin) and I changed `Starting directory:` to `~` and it's doing exactly what. I'll mention it in their Issues. Thanks for your help.
claunia commented 2026-01-31 06:13:03 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 9, 2022):

Thanks for confirming! :)

@DHowett commented on GitHub (Sep 9, 2022): Thanks for confirming! :)
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 Needs-Attention Needs-Tag-Fix Needs-Triage
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#18407
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?