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

running wt should use the current working directory #3125

Closed
stax76 opened this issue Oct 8, 2019 · 4 comments
Closed

running wt should use the current working directory #3125

stax76 opened this issue Oct 8, 2019 · 4 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@stax76
Copy link

stax76 commented Oct 8, 2019

When you start cmd or powershell with ShellExecuteEx or CreateProcess then you can define a working directory, cmd or powershell will start with that working directory but not wt. Is this unsupported or is there a setting?

SHELLEXECUTEINFO shExecInf

shExecInfo.cbSize = sizeof(SHELLEXECUTEINFO);
shExecInfo.fMask = NULL;
shExecInfo.hwnd = hwnd;
shExecInfo.lpVerb = verb.c_str();
shExecInfo.lpFile = path.c_str();
shExecInfo.lpParameters = args.c_str();
shExecInfo.lpDirectory = DirectoryExist(szDir) ? szDir : NULL;
shExecInfo.nShow = Items[i]->HideWindow ? SW_HIDE : SW_NORMAL;
shExecInfo.hInstApp = NULL;

@stax76 stax76 added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Oct 8, 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 Oct 8, 2019
@DHowett-MSFT
Copy link
Contributor

/dup #878

If you set "startingDirectory": null in your profiles, they'll launch in the current working directory. Be careful, though: they'll also launch in System32 when you start WT from the start menu.

We're working on that one.

For anything else, you'll want #607 (which we hope to use to allow you to specify a working directory.)

@ghost
Copy link

ghost commented Oct 8, 2019

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 Oct 8, 2019
@ghost ghost 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 Needs-Tag-Fix Doesn't match tag requirements labels Oct 8, 2019
@stax76
Copy link
Author

stax76 commented Oct 8, 2019

I really appreciate the fast support. I don't use the start menu for that anyway so "startingDirectory": null will be fine for me. Thanks.

@DHowett-MSFT
Copy link
Contributor

Awesome! Happy to help. 😄

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. 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

2 participants