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

Feature Request #2580

New Issue
Closed
opened 2026-01-30 22:58:50 +00:00 by claunia · 6 comments
claunia commented 2026-01-30 22:58:50 +00:00
Owner
Copy Link

Originally created by @pastra98 on GitHub (Jul 5, 2019).

I'm pretty new to using linux, and don't understand much, but my issue is the following:
Every time I use the linux subsystem in windows 10, I want to work in the same directory, where my repos are located. I want to switch to the new terminal app, but every time I open a new linux terminal, it starts out in my windows system 32 directory, whereas I would like it to start where my repositories are located. Using the terminal that's provided with the ubuntu for windows app, I simply made a new shortcut, that starts in my desired location. Any way to do this with the new app?
tldr: start new linux terminal at a specific directory instead of /mnt/c/WINDOWS/system32
sorry if this is the wrong place to ask this.

The json offers the option to specify a starting directory for both powershell and cmd. If possible, it would be awesome to have that same option for a new bash instance.

Originally created by @pastra98 on GitHub (Jul 5, 2019). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> I'm pretty new to using linux, and don't understand much, but my issue is the following: Every time I use the linux subsystem in windows 10, I want to work in the same directory, where my repos are located. I want to switch to the new terminal app, but every time I open a new linux terminal, it starts out in my windows system 32 directory, whereas I would like it to start where my repositories are located. Using the terminal that's provided with the ubuntu for windows app, I simply made a new shortcut, that starts in my desired location. Any way to do this with the new app? **tldr: start new linux terminal at a specific directory instead of /mnt/c/WINDOWS/system32** sorry if this is the wrong place to ask this. <!-- A clear and concise description of what the problem is that the new feature would solve. Describe why and how a user would use this new functionality (if applicable). --> The json offers the option to specify a starting directory for both powershell and cmd. If possible, it would be awesome to have that same option for a new bash instance. <!-- A clear and concise description of what you want to happen. -->
claunia added the Issue-QuestionArea-SettingsResolution-AnsweredProduct-Terminal labels 2026-01-30 22:58:50 +00:00
claunia commented 2026-01-30 22:58:51 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Jul 5, 2019):

The startingDirectory setting works for WSL sessions too. Just add it to the profile you want in the "profiles.json" file. startingDirectory also takes environment variables, so feel free to add that in as one (or create an environment variable for where your repos are located).

@carlos-zamora commented on GitHub (Jul 5, 2019): The `startingDirectory` setting works for WSL sessions too. Just add it to the profile you want in the "profiles.json" file. `startingDirectory` also takes environment variables, so feel free to add that in as one (or create an environment variable for where your repos are located).
claunia commented 2026-01-30 22:58:51 +00:00
Author
Owner
Copy Link

@pastra98 commented on GitHub (Jul 7, 2019):

The startingDirectory setting works for WSL sessions too. Just add it to the profile you want in the "profiles.json" file. startingDirectory also takes environment variables, so feel free to add that in as one (or create an environment variable for where your repos are located).

thanks, just didn't think of simply adding it to the json😄. this helped me a lot...

@pastra98 commented on GitHub (Jul 7, 2019): > The `startingDirectory` setting works for WSL sessions too. Just add it to the profile you want in the "profiles.json" file. `startingDirectory` also takes environment variables, so feel free to add that in as one (or create an environment variable for where your repos are located). thanks, just didn't think of simply adding it to the json😄. this helped me a lot...
claunia commented 2026-01-30 22:58:51 +00:00
Author
Owner
Copy Link

@Luuk34 commented on GitHub (Jul 7, 2019):

   {
            "acrylicOpacity" : 0.5,
            "closeOnExit" : true,
            "colorScheme" : "Campbell",
            "commandline" : "wsl.exe -d Ubuntu",
            "cursorColor" : "#FFFFFF",
            "cursorShape" : "bar",
            "fontFace" : "Consolas",
            "fontSize" : 10,
            "guid" : "{2c4de342-38b7-51cf-b940-2309a097f518}",
            "historySize" : 9001,
            "icon" : "ms-appx:///ProfileIcons/{9acb9455-ca41-5af7-950f-6bca1bc9722f}.png",
            "name" : "Ubuntu",
            "padding" : "0, 0, 0, 0",
            "snapOnInput" : true,
            "startingDirectory" : "/mnt/c/TEMP",
            "useAcrylic" : false
        },

What is missing in this profile, because it is not starting in the startingDirectory?
(and, YES, the directory '/mnt/c/TEMP' does exist)

@Luuk34 commented on GitHub (Jul 7, 2019): ``` { "acrylicOpacity" : 0.5, "closeOnExit" : true, "colorScheme" : "Campbell", "commandline" : "wsl.exe -d Ubuntu", "cursorColor" : "#FFFFFF", "cursorShape" : "bar", "fontFace" : "Consolas", "fontSize" : 10, "guid" : "{2c4de342-38b7-51cf-b940-2309a097f518}", "historySize" : 9001, "icon" : "ms-appx:///ProfileIcons/{9acb9455-ca41-5af7-950f-6bca1bc9722f}.png", "name" : "Ubuntu", "padding" : "0, 0, 0, 0", "snapOnInput" : true, "startingDirectory" : "/mnt/c/TEMP", "useAcrylic" : false }, ``` What is missing in this profile, because it is not starting in the `startingDirectory`? (and, YES, the directory '/mnt/c/TEMP' does exist)
claunia commented 2026-01-30 22:58:51 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Jul 7, 2019):

Took me a bit but finally figured it out. Try "startingDirectory" : "/TEMP".

@carlos-zamora commented on GitHub (Jul 7, 2019): Took me a bit but finally figured it out. Try `"startingDirectory" : "/TEMP"`.
claunia commented 2026-01-30 22:58:51 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jul 7, 2019):

This is because startingDirectory refers to a Windows path.

@DHowett-MSFT commented on GitHub (Jul 7, 2019): This is because `startingDirectory` refers to a Windows path.
claunia commented 2026-01-30 22:58:51 +00:00
Author
Owner
Copy Link

@pastra98 commented on GitHub (Jul 8, 2019):

this is what it looks like for me, now that I've added startingDirectory to the bash settings:
"startingDirectory" : "%USERPROFILE%/Projekte/Programming/Python/GithubRepos",
because at first, it was missing startingDirectory.

@pastra98 commented on GitHub (Jul 8, 2019): this is what it looks like for me, now that I've added startingDirectory to the bash settings: `"startingDirectory" : "%USERPROFILE%/Projekte/Programming/Python/GithubRepos",` because at first, it was missing startingDirectory.
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-Settings Issue-Question Product-Terminal Resolution-Answered
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#2580
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?