-
Notifications
You must be signed in to change notification settings - Fork 11
commands not found #85
Comments
This would occur if we can't locate Quarto on your system. This might be because Quarto isn't on the PATH or it might be because RStudio is installed i a location we don't expect. If it's not on your PATH then we look in the following locations:
Do you know where Quarto is installed? If not, try executing |
Please find it attached
|
Quarto definitely should be found in this configuration! Although I'll be honest and say that I don't know what else to do here as we explicitly looking in What is the result if you execute |
I'm not sure what's going on then. It seems as Quarto isn't found (meaning either the executable isn't there or it isn't callable/invoke-able). What is the file extension of the document you are working with? |
If you just type I have no idea what might be amiss here. The commands seem to have been "registered" as per the keybindings UI |
So the output is the same as in case of render one. The commend is registered but is not executable. Looked on SO and I have basically the same issue as described here: https://stackoverflow.com/questions/49534068/command-not-found-in-vscode-extension However, the top-voted answer is not a root-cause here. I haven't dig any further. Just curious. I was doing installing everything quarto related today - including this extension. Am I the only one who reports it? Can you please try on your own with the released version and check if you have the same? |
You are indeed the only one reporting this right now :-( I reset my system to have all the same versions as you report and things work fine. I sincerely wish I could do more but it's something peculiar to your environment going on here (as all the paths/versions/etc. seem to line up correctly). |
Just to corroborate, I also have this issue, and it is very recent - I was using quarto + VS code's interactive window just yesterday, but now I'm experiencing |
I duplicated the same issue on my Mac. The issue seems to begin with the Quarto extensions of v1.36.0 and later. When I installed v1.35.0 extension, I was able to render again. |
Thanks, that stands to be quite helpful! I just did a diff between v1.35.0 and v1.36.0 and didn't see anything that stood out as potentially causing this issue. It would be helpful to know: (1) Exactly what behavior you are seeing (it is "command not found" or just render appearing not to work) (2) What version of VS Code you are running (3) What version of Quarto you see for |
I do confirm the above. Reverting back to v1.35.0 makes everything work and from v1.36.0 it is not working anymore. I haven't changed |
Hi there, could you also let me know what version of VS Code you are running? Also, could you try invoking Help -> Toggle Developer Tools and then re-try the Quarto commands? (perhaps you will see some JavaScript errors that are occurring). |
My best guess at this point is that JavaScript exception is occurring sometime during the middle of Quarto extension initialization which prevents those commands from being registered. Hopefully the Help => Toggle Developer Tools will give us a clue! |
Just to keep an easily accessible record of it, here are the diffs from 1.35 to 1.36: 5e14c88...9fc7c5a |
VSCode version
I updated to the newest quarto extension and in the developer tools, before any quarto commands I see the following:
How should I understand the above? (I don't have any other records in the console after running other quarto commands.) This is missing in v1.35. |
Okay, we've figured out the problem! You are running version 1.66.2 (which in theory we are compatible with). You can see in this code that we are subscribing to an event that only exists in 1.67: 5e14c88...9fc7c5a#diff-9317a765a7e36179d3a6f2d841bbf7ceaa7449a5beafb1a4812dce59f08fb10dR111-R121 The problem is that that event actually appears to be present in v1.66 but it throws an exception when accessed (which prevents us from further initializing). I realize that you could mitigate this by just updating VS Code, but If you don't mind I'd love to try to resolve this and publish a new version of the extension to try w/ 1.66. Give me an hour or two and I should be able to get that published so you can test. |
Okay, this commit should fix the problem: 646c464 This is available now in an updated release (v1.46.0). Thanks again for your help in diagnosing the problem! |
🎉 all working in v1.46 Thank you! |
I'm having very similar issues as @pawelru did:
|
Try executing Help => Toggle Developer Tools and see if there are any JavaScript errors which are occurring when the Quarto extension is loaded. You might need to also execute the Developer => Reload Window command to cause the extension to re-initialize. |
It's my mistake. I created |
When trying to render a document I have got an error that command is not found. Actually none of the quarto commands works.
and when doing cmd+shift+k
I am using:
Please let me know if you need something more from my side.
In Rstudio I have everything working so it's VSCode related
The text was updated successfully, but these errors were encountered: