Skip to content
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

Should g:jupyter_monitor_console=1 be the default? #11

Open
tcmulcahy opened this issue Jun 27, 2019 · 2 comments
Open

Should g:jupyter_monitor_console=1 be the default? #11

tcmulcahy opened this issue Jun 27, 2019 · 2 comments

Comments

@tcmulcahy
Copy link

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?

@wmvanvliet
Copy link

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."?

@tcmulcahy
Copy link
Author

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.

broesler pushed a commit that referenced this issue Apr 10, 2020
Make the plugin work in neovim.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants