-
Notifications
You must be signed in to change notification settings - Fork 3
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
Can't set path on Mac #14
Comments
I have just installed the extension on my Mac and I was not given the opportunity to set the path either - I was not prompted. |
@russellseymour Do you mean setting the VS Code path or setting CodeSync's external sync path. |
Same here, I installed the extension, restarted Code VS and got the error message The current documentation reads: "VSCode will now prompt for the folder to where you want sync extensions. This should be a folder that syncs to your other computers.". I was not prompted and couldn't find anything in preferences to set the path. The command you are referring to, while existing in Code throws the error described by @piggyslasher. It is also not listed in the documentation under "Commands". Hope it helps. Using MacOS 10.12 Code 1.9.1. |
same on windows 10 x64 + vscode 1.10 |
I have the same problem. It seems like the commands are intermittently available, and it seems like they are only available if there is a file open in my workspace. |
If you're still experiencing this issue on OSX, install Code command line path and then attempt to set the path. Worked for me.. https://code.visualstudio.com/docs/setup/mac |
Just released CodeSync 2.3.0 which allows you to use the rest of the extension even if CodeSync thinks Also closing this issue in favor of #9 |
This extension works like a charm on my PC but not on my Mac.
When restarting VS Code after instralling the extansion it say that it can't find the path in stead of prompting me to define it.
When trying to set it via the command pallet it says:
Error: command 'extension.setSyncPath' not found
The text was updated successfully, but these errors were encountered: