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

VS Code User Data Folder #53

Open
RoyiAvital opened this issue May 6, 2021 · 3 comments
Open

VS Code User Data Folder #53

RoyiAvital opened this issue May 6, 2021 · 3 comments
Labels
bug Something isn't working

Comments

@RoyiAvital
Copy link

VS Code user data folder should be JuliaWin\userdata\.vscode\.
Yet in practice the settings.json file is updated at JuliaWin\packages\vscode\data\.

@heetbeet
Copy link
Owner

This bug is after we moved over to the portable .zip version of VSCode. That version doesn't seem to recognize the commandline arguments to set a user data folder.

The previous approach was to use the full installer and then to fake-install (i.e. extract) it to our wanted location, and make sure the portable launchers take care of setting up the data folders.

I'm not comfortable with extracting the installer, some subtle bugs can creep in, such as not being able to "extract" while another instance of VSCode is running. But I also don't quite like the idea of not being able to set the data directory, I like to keep the "packages" and the "userdata" separate. Will see what I can do about this.

@RoyiAvital
Copy link
Author

Maybe we should open a bug report at VS Code?

@heetbeet
Copy link
Owner

Okay, It seems like there is a difference between how vscode\bin\vscode.cmd and vscode\vscode.exe handles the --user-data-dir and --extensions-dir commandline. I'll have to investigate what the exact difference is and whether we should wrap the .exe rather than the .cmd

When this project started I wasn't able to install the julia extention through code.exe but was able to do it through code.cmd, it might be that I just did something wrong. Odds are that this issue is then easily fixable without having to use the VSCode installer.

@heetbeet heetbeet added the bug Something isn't working label Jun 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants