-
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
Code was not found on your path #41
Comments
Does the customized version use different paths for the extensions directory, settings directory, etc? |
Unfortunately yes, since the application's name is also different. For example my settings's path is But other than application name, I don't find anything else different. |
Hi, sorry to chase on this. Is there any relevant code pointer? I can try figuring out how to add this. |
Sorry it took me a while to get to this, I just published 2.7.0 which lets you set the VSCode executable name and the VSCode user settings path. The new commands are
Update to the latest version and let me know if it works. |
Thank you for adding the support so fast! Sorry it didn't work right out of the gate. When I reinstall the extension, I saw this in my console:
Then I went there and checked that the Then I touched a empty "{}" file named settings.json there. After Reload Window I see this:
I think this is the usual, expected message. Then I use Command Pellate to do setexecutable Then in console:
Not entirely sure what went wrong. Should I seed settings.json with some default params? Thanks! |
Yep after deploying I also ran into this bug, I'm just testing the fix now. 2.7.1 should be available shortly. |
2.7.1 is now released. try that. |
In my 2.7.1 folder I have a empty settings.json file. I didn't create it so I assume it comes with the install. But in console I saw:
Then I went to settings.json and manually added a
that didn't help. :( Still got:
|
Can you try exiting VSCode, deleting the settings.json file, and then launching VSCode again? |
Thank you! after delete settings and restart, it now prompts me to enter path and enter executableName However after all is done. I saw one file in my sync folder:
Do I need to anything extra to make keybindings and settings work? |
Can you paste your CodeSync logs here? They are available in the Output view (View > Output > CodeSync) |
Oh this is helpful:
The actual path to settings is: For some reason it can output God this is messy. |
Yes if extensions.json is being created that means the CLI path was found. Once you manually set the VSCode settings path for CodeSync whenever you try and export settings this log line should appear in the CodeSync logs.
|
My god what are these people thinking. The custom path contains special characters like '/Users/abc/Library/Application Support/VS Code @ My Wonderful Company/User/`
Thank you. |
What OS are you on? I tried this in Linux and I am not getting this error. |
@golf1052 Just regular MacOS. I'm total noob with js but this error, is it inside the extension or is it inside the vscode's code? |
This is a VSCode error, the problem with nailing down where this error is, is that VSCode can't output the stacktrace of extensions. |
ah any way I can help debug this? My settings file contains comment in the form of "// comments", not sure if this is interfering with anything. |
If you're able to setup the extension locally you should be able to get a stack trace while debugging. That would be very helpful. |
okey finally got to it and here's where it's complaining:
|
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:
CodeSync version:
CodeSync log:
Issue:
![Screen Shot 2020-04-18 at 3 26 25 PM](https://user-images.githubusercontent.com/5747393/79672654-fc7ff100-8188-11ea-9e3f-06acd0403e92.png)
Our company uses a customized version of vscode and has a different command, so instead of
code
, we have other variant, for examplecodeabcdefg
.Can we make this configurable as a setting?
Thanks!
The text was updated successfully, but these errors were encountered: