-
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
codesync: export settings - command not found #27
Comments
Did you get this error right after you installed the extension? |
This extension has been running for a while and restarting VS Code doesn't affect the error mentioned. |
Did this work in the past for you? |
I have not tried any codesync commands before and of the ones I just tried they all say, 'not found' EDIT; the dropdown list shows them when I first start typing: |
Is T: a different drive? |
T: is a network share, on my domain. |
Is there an easier way to change that location other than to uninstall and reinstall to get that prompt? |
Open the command prompt and look for |
That says |
Ok, my thinking is that remote drives don't work for some reason. I'll set one up and take a look at what's going on. |
Ok try reinstalling the extension and setting the path. The commands don't activate until CodeSync loads and I'm guessing an exception is being thrown while it's loading which is preventing you from using any commands. |
Alright, will do. |
It appears the same thing is happening, with this local disk path: D:\Cloud Storage\OneDrive\CodeSync on both systems. |
Ok could you try installing this version of CodeSync: https://1drv.ms/u/s!AnkZumdCoH3t0fw9F44SriLJtaUtRw I've wrapped the startup code in a try catch and any exception should be logged. Here are the instructions on installing an extension from a VSIX Post the log here when you've tried this version. |
Okay, this is strange...I am able to use those commands now. "What did you do Willis?" |
Nothing that should have caused this issue changed between 2.4.0 and this version, I guess a reinstall helped. Try your original location again. If that works I guess the issue is solved. |
yeah, I just tried my T: and that still doesn't work. |
ALright, more strangeness, It keeps not working on my T: drive then I close Code and reopen and things work, but it has changed my codesync path to a directory on C: drive C:\Users\USER\OneDrive\Apps\code-sync |
The log is under the Output tab I believe. Ctrl+Shift+U opens it. |
OKay, got that but nothing is showing up in there when that |
Is CodeSync selected in the output window? |
settings.ts |
Some good news, I was able to load a blank, ie no extensions, Code install and install the 2.5.1VISX file and import the list from the T: drive. |
I tried setting up a network share and everything worked fine for me. |
I was able to set up my laptop and another desktop and just tried a hunch after Code loaded I tried the |
If you are reporting an issue/bug please fill in your VSCode version, CodeSync version, and if you are on version 2.4.0 and above the CodeSync log from the CodeSync output channel. Thanks!
If you are requesting a feature feel free to clear this template.
VSCode version:
1.17.0
CodeSync version:
2.4
CodeSync log:
Issue: I tried
codesync: export settings
but it said no command was found, in the upper bar of VSCode.My
local-settings.json
is empty and I wanted to check the extensions being exported on my systems.Not sure if this is a new VSCode version issue or not, as I never tried it before.
The text was updated successfully, but these errors were encountered: