Replies: 1 comment 1 reply
-
Thanks, this looks really cool! This attaches to a plain python file with code chunk marker comments, right? So if I we add those markers to the synchronized otter buffer of https://github.com/jmbuhr/otter.nvim, you could attach it to this hidden buffer, which would then keep both things in sync. A quick word from educator-me: If your code cells take a long time to execute and even caching takes too long, it is most likely a sign that you are better off refactoring this part into a script or function and track it with a proper workflow/dependency tool such as |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
thanks for this nvim addin it’s really great.
I see that quarto-nvim takes advantages of many other addins so I wanted to bring your attention to https://github.com/kiyoon/jupynium.nvim
We are using it and found it to be a major productivity boost.
This idea is that you can send code to jupyter for visualisation. The advantage over preview arise when some cells require long execution and even loading back the cache take a lot of time. This is always the case in our field.
You could even push it to send as well in a R console in a tmux pane (most of us dislike working in a notebook cell) and essentially keep the notebook session 'cleaner'
Hope you find jupynium worth a look
Beta Was this translation helpful? Give feedback.
All reactions