You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This one might be a bit controversial: Given that you need configuration in order to see output in jupyter console/qtconsole, I'd recommend making g:jupyter_monitor_console=1 the default. This would make jupyter-vim have a less steep learning curve. It's a lot easier to disable the console once you have the tool working than to be running the tool and be frustrated that you don't see anything happening. We can even output a message to the console explaining how to disable it. Thoughts?
The text was updated successfully, but these errors were encountered:
I dislike the Vim buffer monitoring Jupyter. Can't we just output a message to the status line such as "Sent X lines to kernel. Press enter in the console to see the result."?
I dislike it too and I'm only suggesting it to make the first experience more forgiving. A status line message could help, but we'd also need to tell people to enable the configuration to see the console output too.
This one might be a bit controversial: Given that you need configuration in order to see output in jupyter console/qtconsole, I'd recommend making g:jupyter_monitor_console=1 the default. This would make jupyter-vim have a less steep learning curve. It's a lot easier to disable the console once you have the tool working than to be running the tool and be frustrated that you don't see anything happening. We can even output a message to the console explaining how to disable it. Thoughts?
The text was updated successfully, but these errors were encountered: