-
Notifications
You must be signed in to change notification settings - Fork 9
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
Plots in VSCode Jupyter notebook opens in browser instead of below cell #34
Comments
Hmm, that's a little surprising. What happens if you remove the |
No change, still opens up the browser. Think I might have left it in there after trying different stuff out to get it to work 😅 |
Okay, can you try running |
Doesn't fix it. Still plots in the browser but now in a frame |
My guess here is that there is an upstream issue, since this doesn't display anything: HTML(repr("text/html", Plot(x=1:10))) It's possible that VSCode's Jupyter disables the javascript that the plot's show method depends on. |
Although, tried it on another machine and as you said it did nothing (same versions of PlotlyLight and Julia, but VSCode 1.84.1) |
I think it works if you run |
You're right, but I swear it worked without it on the other machine after kernel restart. Not on this one though. |
Think you might be able to use |
HI @joshday, the above pull request above solves this for me in VSCode (and still works correctly in REPL), I don't have a way to test it on other systems but don't see why it would break anything. Could you review and merge it if you're happy please? |
Same as the other issue: PR is in your own fork and not here. |
Fixed on master/in v0.8.0 |
Hi,
I'm trying to use the example plot script, however I end up with the plot opening up in the browser instead of below the cell in Jupyter notebook in VSCode.
The output of that is:
Running the same code in REPL creates the plot in a window withing VSCode which is how I would expect it to behave.
I'm running on Windows:
Julia v1.9.0
VSCode v1.82.3
PlotlyLight v0.7.4
The text was updated successfully, but these errors were encountered: