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

NOMERGE: Always use VSCODE_PORTABLE env when portable #733

Merged

Conversation

chase9
Copy link

@chase9 chase9 commented Dec 11, 2018

This change seems too simple to me, so I wouldn't find someone else looking over it before merging. I'm wondering, why the extension was set to save to application support in the first place when in portable mode, especially if all other OS's were set to save to VSCODE_PORTABLE?

Short description of what this resolves:

This attempts to resolve #684, support portable version on mac

Changes proposed in this pull request:

  • When in portable mode, macs environment operates the same as other OS's. That is, it writes to VSCODE_PORTABLE instead of application support.

I believe this is the proper behavior, as while portable we don't want any data to be saved to any part of the fine system other than the portable directory.

How Has This Been Tested?

Tested on VSCode 1.29.1, running the latest clone of code-settings-sync
macOS 10.14.2, MacBookPro11,3.

Tested initial gist creation, successful settings upload then download.

Checklist:

  • I have read the contribution guidelines.
  • My change requires a change to the documentation and Github Wiki.
  • I have updated the documentation and Wiki accordingly.

Mac will no longer use Application Support while in portable mode
@shanalikhan shanalikhan merged commit 8cac523 into shanalikhan:v3.2.3 Dec 11, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants