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

Support for --user-data-dir #65

Closed
tleepa opened this issue Oct 30, 2016 · 4 comments
Closed

Support for --user-data-dir #65

tleepa opened this issue Oct 30, 2016 · 4 comments
Labels
depends on Depends on issues from VS Code enhancement

Comments

@tleepa
Copy link

tleepa commented Oct 30, 2016

When running VSCode.exe you can specify this flag to point to the user data directory.
However, the extension looks for the process.env.appdata to set up the base to build projectFile path (extension.js, var appdata = ... in the getProjectFilePath function).
It would be great, if it could support the --user-data-dir.
One way could be to start with process.env.VSCODE_HOME and leave out the channelPath.

Please, note that I am not a developer and I only did "find" the issue. The above "solution" is just a general idea and Windows specific. Linux supports this flag too (most likely so does Mac)...

@alefragnani
Copy link
Owner

Hi @tleepa ,

The idea behind projectManager.projectsLocation is to allow the user to define a different location for its projects.json file, either for sharing, _ sync_ or custom rules. You could use that, if you always use the same --user-data-dir. (just a tip).

I don't know if there is an API to access --user-data-dir parameter. In fact there are some opened issues around VS Code internal folders (data, extensions, etc). But it makes sense, if it allows you to define a different folder for its data, to use this folder in the extension. Even better if process.env.appData should be updated to reflect --user-data-dir.

Stay tuned.

@alefragnani
Copy link
Owner

Depends on microsoft/vscode#2741

@alefragnani alefragnani added the depends on Depends on issues from VS Code label Mar 19, 2017
@medikoo
Copy link

medikoo commented May 18, 2017

I approached very same problem, hopefully they provide requested API in VSCode

@alefragnani
Copy link
Owner

There is no ETA for the VS Code API to be available, and so, I'm closing the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
depends on Depends on issues from VS Code enhancement
Projects
None yet
Development

No branches or pull requests

3 participants