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.

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

Proposal: Evolution of startingDirectory #9991

Closed
zadjii-msft opened this issue Apr 29, 2021 · 7 comments
Closed

Proposal: Evolution of startingDirectory #9991

zadjii-msft opened this issue Apr 29, 2021 · 7 comments
Labels
Area-Settings Issues related to settings and customizability, for console or terminal Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Issue-Question For questions or discussion Product-Terminal The new Windows Terminal. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@zadjii-msft
Copy link
Member

What if we had something like:

{
    "ignoreStartingDirectories": bool,
}

as a global setting? Then we'd just never use the startingDirectory for a profile, and always use the CWD of the Terminal. That seems like a big hammer, but there might be folks who are all setting "startingDirectory": "." for all their profiles, where this would be an easier solution.

Alternatively:
What about wt --cwd C:\foo new-tab? That would make sure that the Terminal's CWD is set to C:\foo, not just the CWD of that tab.
That would work better for things like the context menu, that might want subsequent tabs to open in the same CWD, but poorly for wt -w 0 --cwd C:\foo nt

@zadjii-msft zadjii-msft added ⛺ Reserved For future use Area-Settings Issues related to settings and customizability, for console or terminal Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Issue-Question For questions or discussion Product-Terminal The new Windows Terminal. and removed ⛺ Reserved For future use labels Apr 29, 2021
@zadjii-msft zadjii-msft added this to the Terminal Backlog milestone Apr 30, 2021
@jerblack
Copy link

jerblack commented Jun 4, 2021

Far more important to me would be an option where you don't interfere in the startup at all and just open my WSL terminals in ~. The fact that you havce a checkbox option in your settings UI that causes Terminal to open in /mnt/c/Windows/system32 but nothing at all to say "just stay out of the way and don't interfere with the Ubuntu default behavior" is insane to me.

@DHowett
Copy link
Member

DHowett commented Jun 4, 2021

just stay out of the way and don't interfere with the Ubuntu default behavior

Bad news: Opening in whatever directory you run it from is the WSL launcher's default behavior. That checkbox is, quite literally, a paraphrased version of "Do the default behavior for the thing you are launching."

@DHowett
Copy link
Member

DHowett commented Jun 4, 2021

(That checkbox is, to put it another way, "do not interfere in the startup at all.")

@jerblack

This comment has been minimized.

@DHowett

This comment has been minimized.

@zadjii-msft
Copy link
Member Author

Oh my god I must have totally forgotten about #4637, because that's the same thing. That's on me.

/dup #4637

@ghost
Copy link

ghost commented Dec 9, 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 ghost closed this as completed Dec 9, 2021
@ghost ghost added the Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. label Dec 9, 2021
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Settings Issues related to settings and customizability, for console or terminal Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Issue-Question For questions or discussion Product-Terminal The new Windows Terminal. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

3 participants