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

cannot configure starting directory in GUI when its default value is set to null #13476

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

Originally created by @taroxd on GitHub (Apr 16, 2021).

Originally assigned to: @carlos-zamora, @PankajBhojwani on GitHub.

Windows Terminal version (or Windows build number)

10.0.19042.928 1.7.1033.0

Other Software

No response

Steps to reproduce

First, Set

    "profiles":
    {
        "defaults":
        {
            "startingDirectory": null
        },
...

This makes the default starting directory to the parent process, which is my expected behaviour.

After that, however, the starting directory for individual shell cannot be configured in the GUI. The Browse button is grayed out. See the screenshot:
image

Expected Behavior

The starting directory should be configurable in the GUI.

Actual Behavior

See Steps to reproduce.

Originally created by @taroxd on GitHub (Apr 16, 2021). Originally assigned to: @carlos-zamora, @PankajBhojwani on GitHub. ### Windows Terminal version (or Windows build number) 10.0.19042.928 1.7.1033.0 ### Other Software _No response_ ### Steps to reproduce First, Set ``` "profiles": { "defaults": { "startingDirectory": null }, ... ``` This makes the default starting directory to the parent process, which is my expected behaviour. After that, however, the starting directory for individual shell cannot be configured in the GUI. The `Browse` button is grayed out. See the screenshot: ![image](https://user-images.githubusercontent.com/6070540/114979591-b9507f00-9ebd-11eb-9c4a-32e93e0e7145.png) ### Expected Behavior The starting directory should be configurable in the GUI. ### Actual Behavior See `Steps to reproduce`.
claunia commented 2026-01-31 03:43:45 +00:00
Author
Owner
Copy Link

@skyline75489 commented on GitHub (Apr 16, 2021):

Does #8904 covers this?

@skyline75489 commented on GitHub (Apr 16, 2021): Does #8904 covers this?
claunia commented 2026-01-31 03:43:45 +00:00
Author
Owner
Copy Link

@taroxd commented on GitHub (Apr 16, 2021):

Hopefully it does. I will wait for it to be resolved.

@taroxd commented on GitHub (Apr 16, 2021): Hopefully it does. I will wait for it to be resolved.
claunia commented 2026-01-31 03:43:45 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 16, 2021):

Yea, it sounds like #8904 will take care of this

/dup #8904

@zadjii-msft commented on GitHub (Apr 16, 2021): Yea, it sounds like #8904 will take care of this /dup #8904
claunia commented 2026-01-31 03:43:45 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Apr 16, 2021):

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 (Apr 16, 2021): 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!
claunia commented 2026-01-31 03:43:45 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Apr 16, 2021):

However, what we have today in 1.7 is broken and needs to be fixed.

I'm going to use this bug to track fixing it for servicing, as I am not going to backport a design change 😄

@DHowett commented on GitHub (Apr 16, 2021): However, what we have today in 1.7 is broken and needs to be fixed. I'm going to use this bug to track fixing it for servicing, as I am not going to backport a design change :smile:
claunia commented 2026-01-31 03:43:45 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (May 25, 2021):

:tada:This issue was addressed in #9862, which has now been successfully released as Windows Terminal Preview v1.9.1445.0.🎉

Handy links:

@ghost commented on GitHub (May 25, 2021): :tada:This issue was addressed in #9862, which has now been successfully released as `Windows Terminal Preview v1.9.1445.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.9.1445.0) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
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-SettingsUI Issue-Bug Priority-1 Product-Terminal Resolution-Fix-Committed
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#13476
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?