Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

By default, start in the home folder when opening a linux shell #1759

Closed
djk2004 opened this issue Jul 1, 2019 · 2 comments
Closed

By default, start in the home folder when opening a linux shell #1759

djk2004 opened this issue Jul 1, 2019 · 2 comments
Labels
Area-Settings Issues related to settings and customizability, for console or terminal Issue-Task It's a feature request, but it doesn't really need a major design. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@djk2004
Copy link

djk2004 commented Jul 1, 2019

Summary of the new feature/enhancement

When opening a new Linux shell, the starting folder is /mnt/c/WINDOWS/system32. Instead, use the current user's home folder. This would match the current behavior with the legacy console.
Generally, most users would not want to work in the system32 folder. However, starting from the home folder would be expected behavior.

Proposed technical implementation details (optional)

Simply change the default starting path to the user's home folder. This could either be the Windows user's home folder, or the Linux shell home folder at /home/. Alternatively, the profile configuration could also include a property that lets the user set the starting folder per profile.
@djk2004 djk2004 added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Jul 1, 2019
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jul 1, 2019
@oising oising added Area-Settings Issues related to settings and customizability, for console or terminal Issue-Task It's a feature request, but it doesn't really need a major design. and removed Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Needs-Tag-Fix Doesn't match tag requirements labels Jul 1, 2019
@Kirlac
Copy link

Kirlac commented Jul 2, 2019

#592 discusses the configurability of this

There is also a workaround in the comments for that issue - adding ~ to your wsl commandline setting will start in your linux home dir: #592 (comment)

I agree it would make sense for profiles.json to include this for WSL by default

@DHowett-MSFT
Copy link
Contributor

Honestly, this should just be a dupe of 592.

@DHowett-MSFT DHowett-MSFT added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Jul 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Area-Settings Issues related to settings and customizability, for console or terminal Issue-Task It's a feature request, but it doesn't really need a major design. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@oising @Kirlac @DHowett-MSFT @djk2004