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

Open folders in a predefined vs code environments #69260

Closed
tsathis opened this issue Feb 23, 2019 · 2 comments
Closed

Open folders in a predefined vs code environments #69260

tsathis opened this issue Feb 23, 2019 · 2 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s) extensions Issues concerning extensions feature-request Request for new features or functionality

Comments

@tsathis
Copy link

tsathis commented Feb 23, 2019

I already know there is a option called work-space , but this does not addressed my issue.
This is the feature what I need,
Assume that I am using vs code for different purposes. As an example: I use vs code for,

  1. Web designing (HTML, CSS, JS)
  2. C++ Programming

When I'm working with HTML, CSS, JS I need to have some special extensions, tasks, launch properties etc. On the other hand when I'm working with C++ I need different extensions, tasks and launch properties. Assume I have two predefined environment for both separately. And these two environments will have only the extensions and other properties that are needed only for each environment. Now I need to open a folder to start a C++ project, so I open this folder with terminal command by adding a the environment name as argument. i.e. code . -env MyCppEnvironment or code . -env WebDesigning.

You may suggest that I could use workspaces option for this. But in my point of view I see workspace as follows,

I open a workspace for C++. code cppProject1.code-workspace. Then I configure the needed properties of the workspace(extensions, tasks, launch properties etc.), then add folders of related project to workspace. And work with it. So then we have to make the workspace again and again for each project.

@joaomoreno joaomoreno assigned bpasero and sandy081 and unassigned joaomoreno Feb 26, 2019
@bpasero bpasero added feature-request Request for new features or functionality extensions Issues concerning extensions labels Feb 27, 2019
@bpasero bpasero removed their assignment Feb 27, 2019
@sandy081 sandy081 added the *duplicate Issue identified as a duplicate of another issue(s) label Feb 27, 2019
@sandy081
Copy link
Member

Looks dup of #39272

@vscodebot
Copy link

vscodebot bot commented Feb 27, 2019

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for existing issues here. See also our issue reporting guidelines.

Happy Coding!

@vscodebot vscodebot bot closed this as completed Feb 27, 2019
@vscodebot vscodebot bot locked and limited conversation to collaborators Apr 13, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s) extensions Issues concerning extensions feature-request Request for new features or functionality
Projects
None yet
Development

No branches or pull requests

4 participants