ENH Start a new Ipython kernel from vim#94
Conversation
This is a bit hacky, but it works well enough: 1. generate a new random ID 2. use the subprocess to start a completely new IPython kernel process with that ID. This may not even be the same Python version that vim is running (this is a feature, not a bug) 3. connect to this kernel Currently, the kernel is automatically killed at exit.
|
Another also somewhat hacky solution is This has the benefit that it accepts the same arguments as |
|
thanks both for the contributions here, I'll take a look and get this is later on today. |
|
Talking this over with @minrk, we'll be better off using KernelManager to do this, so I'll merge this for now, but extend it to use that (less hacky) machinery |
|
Thanks for the contribution, @luispedro - I rebased this commit and it became 80eecbd. Then I just used the KernelManager machinery to start the kernel instead (cf54530). Let me know how that goes for you. |
Conflicts: ftplugin/python/ipy.vim
|
Seems this PR can be closed 😄 |
The mappings use <LocalLeader> (and not <Leader>).
This is a bit hacky, but it works well enough:
with that ID. This may not even be the same Python version that vim
is running (this is a feature, not a bug)
Currently, the kernel is automatically killed at exit.