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

how to specify startingdirectory when terminal launch? #8192

Closed
candrewtemenoscom opened this issue Nov 7, 2020 · 5 comments
Closed

how to specify startingdirectory when terminal launch? #8192

candrewtemenoscom opened this issue Nov 7, 2020 · 5 comments
Labels
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

@candrewtemenoscom
Copy link

I tried to specifying it in startingdirectory in setting.json. But it does not work. I would like to set the directory when I launch the terminal.

@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 Nov 7, 2020
@LuanVSO
Copy link
Contributor

LuanVSO commented Nov 7, 2020

how does it not work?
mind sharing your settings.json?

@ghost
Copy link

ghost commented Nov 8, 2020

@zadjii-msft
Copy link
Member

Yea you gotta give us some more info. What have you set it to? What's the commandline you're using? By any chance, are you using a WSL distro (which might make this #7197)?

@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 Nov 8, 2020
@candrewtemenoscom
Copy link
Author

It is working now. I put the startingdirectory property in the wrong section. Now I moved it to the default profile. Thanks for the quick response and the pointers.

A quick suggestion. I find that sometimes it is not easy to know where to set the property and its value especially when there are multiple nested properties. I find that the swagger doc for setting properties in its json file quite intuitive in which it pre-specify (but commented out) all the optional property and users can choose to enable it by uncommenting out the property. It prevents making mistakes.

@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 Nov 9, 2020
@zadjii-msft
Copy link
Member

I'm glad you were able to figure it out!

We actually previously would include all the possible properties in the settings file, but it turned out to be much to unwieldy. There's just a lot of settings, and it largely made the file harder to read. Hopefully this won't be much of an issue when the settings UI ships (soonTM)

@zadjii-msft zadjii-msft added Issue-Question For questions or discussion Resolution-Answered Related to questions that have been answered labels Nov 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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

3 participants