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

Start new tab in last used tab working dir path [BUG] #17863

New Issue
Closed
opened 2026-01-31 05:56:39 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 05:56:39 +00:00
Owner
Copy Link

Originally created by @QuAzI on GitHub (Jul 5, 2022).

It is better to use last working dir for new tab instead of first random chosen path
image

Originally created by @QuAzI on GitHub (Jul 5, 2022). It is better to use last working dir for new tab instead of first random chosen path ![image](https://user-images.githubusercontent.com/1897605/177285731-1e9993ba-3908-4c9c-b443-a5a75c4da56c.png)
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 05:56:39 +00:00
claunia commented 2026-01-31 05:56:41 +00:00
Author
Owner
Copy Link

@QuAzI commented on GitHub (Jul 5, 2022):

As example I started wt in any dir. Then I ran through FM (Explorer, TotalCommander... doesn't matter) CMD file which starts two copies of nodejs (es5, es6) in the same tab.

CMD example

start wt -d ./src/ApplicationFrontend/  pwsh.exe -NoExit -command npm run watch-debug-es5-only; split-pane -d ./src/ApplicationFrontend/ powershell.exe -NoExit -command npm run watch-debug-es6-only

now my script crashes because start path broken. It is not script path and not last used path. It means even if I run my script from wt - it crashes if wt started not from current path. So I must close all tabs and start from begin

[error 2147942667 (0x8007010b) when launching `pwsh.exe -NoExit -command npm run watch-debug-es5-only']
Could not access starting directory "./src/ApplicationFrontend/"
@QuAzI commented on GitHub (Jul 5, 2022): As example I started wt in any dir. Then I ran through FM (Explorer, TotalCommander... doesn't matter) CMD file which starts two copies of nodejs (es5, es6) in the same tab. CMD example ``` start wt -d ./src/ApplicationFrontend/ pwsh.exe -NoExit -command npm run watch-debug-es5-only; split-pane -d ./src/ApplicationFrontend/ powershell.exe -NoExit -command npm run watch-debug-es6-only ``` now my script crashes because start path broken. It is not script path and not last used path. It means even if I run my script from wt - it crashes if wt started not from current path. So I must close all tabs and start from begin ``` [error 2147942667 (0x8007010b) when launching `pwsh.exe -NoExit -command npm run watch-debug-es5-only'] Could not access starting directory "./src/ApplicationFrontend/" ```
claunia commented 2026-01-31 05:56:41 +00:00
Author
Owner
Copy Link

@QuAzI commented on GitHub (Jul 5, 2022):

And even this workaround in start of script doesn't helps

cd %~dp0
@QuAzI commented on GitHub (Jul 5, 2022): And even this workaround in start of script doesn't helps ``` cd %~dp0 ```
claunia commented 2026-01-31 05:56:41 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 7, 2022):

Wait what exactly is the bug here?

Do you have "New instance behavior" set to "Create a new window" or "Attach to the most recent..."? Trying this out locally, I got the same error message when the tab was opening in an existing WT window. When it gets sent to a new window though, it seems to work fine

I was sure this was on the backlog somewhere... found it, or at least what I've been using to track this: #5506

@zadjii-msft commented on GitHub (Jul 7, 2022): Wait what exactly is the bug here? Do you have "New instance behavior" set to "Create a new window" or "Attach to the most recent..."? Trying this out locally, I got the same error message when the tab was opening in an existing WT window. When it gets sent to a new window though, it seems to work fine I was sure this was on the backlog somewhere... found it, or at least what I've been using to track this: #5506
claunia commented 2026-01-31 05:56:41 +00:00
Author
Owner
Copy Link

@QuAzI commented on GitHub (Jul 11, 2022):

"Attach to the most recent..." of course because it is more comfortable to have one window with multiple tabs. But it doesn't mean that this window combine only instances with same working dir.

@QuAzI commented on GitHub (Jul 11, 2022): "Attach to the most recent..." of course because it is more comfortable to have one window with multiple tabs. But it doesn't mean that this window combine only instances with same working dir.
claunia commented 2026-01-31 05:56:41 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 11, 2022):

Okay, yea, that'll be fixed by #5506 then. Thanks!

/dup #5506

@zadjii-msft commented on GitHub (Jul 11, 2022): Okay, yea, that'll be fixed by #5506 then. Thanks! /dup #5506
claunia commented 2026-01-31 05:56:42 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jul 11, 2022):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Jul 11, 2022): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
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 Issue-Feature Resolution-Duplicate
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#17863
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?