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

[FR] Add ability to inherit starting directory when launching from the context of other apps #9349

Closed
Kein opened this issue Mar 2, 2021 · 4 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Issue-Question For questions or discussion Needs-Attention The core contributors need to come back around and look at this ASAP. Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Resolution-Answered Related to questions that have been answered

Comments

@Kein
Copy link

Kein commented Mar 2, 2021

Description of the new feature/enhancement

Just as the title say, inherit the working directory from the context of the app that launches it if possible.
For example, Total Commander has a command line you can launch default cmd from and it will inherit current working/active directory.

Proposed technical implementation details (optional)

@Kein Kein added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Mar 2, 2021
@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 Mar 2, 2021
@zadjii-msft
Copy link
Member

You can already do this with the commandline args to wt.exe. If you launch wt.exe -d . it will inherit the CWD of the caller. wt -d c:\windows\system32 and it'll launch in c:\windows\system32. Does that work for you?

@zadjii-msft zadjii-msft added the Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something label Mar 2, 2021
@Kein
Copy link
Author

Kein commented Mar 2, 2021

Yes it works albeit not exactly the way current cmd does it.
Hmm, is there a way to set config up so if Terminal is called directly via shortcut on desktop or tile in Start it will use startingDirectory, otherwise, it will use -d . by default? I know I can use -d . as a default startup command but this will apply to every single launch, which is not always desirable.

Basically, is there way to somehow distinguish context?

@ghost ghost added Needs-Attention The core contributors need to come back around and look at this ASAP. and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels Mar 2, 2021
@zadjii-msft
Copy link
Member

Unfortunately, no. There's no good way to distinguish between those types of launches. #3547, #878 (comment) and #878 (comment) have more details.

@zadjii-msft zadjii-msft added Issue-Question For questions or discussion Resolution-Answered Related to questions that have been answered labels Mar 2, 2021
@Kein
Copy link
Author

Kein commented Mar 2, 2021

That' unfortunate. At least you could have alias -d . to empty -d or another flag that will do -d . automatically to reduce the crumblesomeness of the approach.

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. Issue-Question For questions or discussion Needs-Attention The core contributors need to come back around and look at this ASAP. Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Resolution-Answered Related to questions that have been answered
Projects
None yet
Development

No branches or pull requests

2 participants