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

When VSC has no open folder, please have "Integrated Terminal" open in same default folder #13718

Closed
kumueric opened this issue Oct 14, 2016 · 1 comment
Assignees
Labels
*extension-candidate Issue identified as good extension implementation

Comments

@kumueric
Copy link

  • VSCode Version: Code 1.6.1 (9e4e44c, 2016-10-13T16:21:53.542Z)
  • OS Version: Windows_NT ia32 10.0.14393
  • Extensions: abusaidm.html-snippets-0.0.17, donjayamanne.python-0.4.2

Steps to Reproduce:

  1. File --> "Close Folder"
  2. Push "Open Folder" & notice that VSC opens in a "default" folder [Now push CANCEL]
  3. View --> "Integrated Terminal" & notice that VSC opens "way up" in the user's home folder.

Please update VSC so that #3 opens into the same folder as #2 WHEN THERE IS NO OPEN FOLDER!

NOTE: If you have specified "Open Folder," then View --> "Integrated Terminal" opens in the folder that you "Opened." My request is for the case when there is NO OPEN FOLDER.

@Tyriar
Copy link
Member

Tyriar commented Oct 14, 2016

I'd prefer not to bring this in due to the fact that it makes the path that launches inconsistent depending on whether the workspace is empty or has a folder. I recommend installing the Terminal Here extension to open the folder of the current file. If you need this to apply only when the workspace is empty I'd be glad to add it as an option on that extension, in which case file an issue here.

@Tyriar Tyriar closed this as completed Oct 14, 2016
@Tyriar Tyriar added the *extension-candidate Issue identified as good extension implementation label Oct 14, 2016
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*extension-candidate Issue identified as good extension implementation
Projects
None yet
Development

No branches or pull requests

2 participants