Startup script repl

[mrsalo]

#391

[justinmk]

what is step-by-step the workflow for using this? That should be mentioned in the README.

I would think invoking something from Nvim would be more useful, rather than making the user choose from a list.

[mrsalo]

I updated the README. I don't know if this is already enough documentation.
I would also prefer the invocation through nvim, but it has one flaw:
When I use the :term feature to start a terminal and then e.g. IPython I am perfectly able to connect to the current instance. But the current buffer (the one i get using nvim.current.buffer) is the terminal buffer where IPython runs and not the one I wanted to modify through the REPL initially.
Hope this gif makes it a little bit clearer:

[justinmk]

Actually, I don't think it makes sense to put this in pynvim repo. Most pynvim users won't have the scripts/ AFAIK. So if anything this should be a plugin or maybe contrib/ in the neovim repo.

[mrsalo]

Ok, what would you think of putting it in the pynvim module or in a submodule and not as a startup script but as a function?
If you think it's not worth the hassle that`s also fine. Just found it easier to use than the standard procedure.

[justinmk]

Ok, what would you think of putting it in the pynvim module or in a submodule and not as a startup script but as a function?

That was my first thought. I guess it makes sense because then Nvim core only needs to look for that function. The function can be mentioned by nvim_set_client_info. I think open_repl might be a good name.

pynvim/pynvim/plugin/host.py

Lines 167 to 168 in c608e53

	self.nvim.api.set_client_info(
	name, VERSION.__dict__, "host", host_method_spec,

Add open_repl to host_method_spec.