-
Notifications
You must be signed in to change notification settings - Fork 31
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
Confused about code execution #103
Comments
We haven't written up the docs on this (apologize for the delay!). When we do, we'll note that Python chunks currently can't be executed (I'm guessing that is what you are seeing). This is because we call the Jupyter extension to execute Python code and it in turn expects that an active text editor is in the foreground in order to work correctly. It should however currently work for R and Julia (we'd definitely like to make it work for Python but we need some outside help for that to happen) |
Ahh, I see, yes I was trying to execute Python code. Sounds good, I'll wait patiently; thanks for all your hard work regardless! Possibly related this issue, which I think has also come up in the context of jupytext. Also see: https://marketplace.visualstudio.com/items?itemName=congyiwu.vscode-jupytext |
Yeah, that one is about their supporting other plain text formats for code execution. Here the visual editor is a "custom editor" so fails their check for |
I'm glad I found this thread, I thought there was an issue with my VScode. It would be nice to have this stated in the documentation. |
Fore reference: |
Currently, it is possible to execute Python cells individually in the visual editor in Positron, but not in VS Code. |
FYI, positron repository: https://github.com/posit-dev/positron |
For Quarto VSCode version 1.70 in the changelog it was mentioned:
For my visual editor I cannot execute cells though. I tried changing the keybinds but they seem to only work in the source mode.
Am I misunderstanding the changelog comment or is this a bug on my end?
Versioning:
The text was updated successfully, but these errors were encountered: