[enhancement] Add an option to clear screen every time code is sent

[jagjordi]

Some times you want to run code in a clean terminal, you would do that with clear-screen command in IPython. It would be nice if some sort of setting through a global variable could be enabled so every time you send code from vim :JupyterRunFile the clear-screen command also gets send just before.

Regards.

[tinmarino]

Brief: I've just coded this feature (1939006), jump to 'get-it' if you want to use it.
Reason: That is a pretty good idea. A feature like that can permit many things.
Warning: Your history will be filled of clear-screen command if we don't solve #24 before.

Now: I added 4 variables

1. b:jupyter_exec_before: Send another command before
2. b:jupyter_exec_pre: prepend
3. b:jupyter_exec_post: append
4. b:jupyter_after_after: Send another command after

Get it:

In you jupyter-vim directory:

git fetch
git check dev

In your vimrc:

autocmd FileType python let b:jupyter_exec_before = 'clear-screen'

Before: (Do not do it)

python3 _jupyter_session.client.send_save = _jupyter_session.client.send
python3 _jupyter_session.client.send = lambda cmd : _jupyter_session.client.send_save('print("pre")') and _jupyter_session.client.send_save(cmd) and _jupyter_session.client.send_save('print("post")')

After: (More implementation independent)

autocmd FileType python let b:jupyter_exec_before = 'clear-screen'

I'll try to solve #24 which will be annoying for (before|after)_each

[tinmarino]

Tell me if you like this way. Thank you for raising the issue: for the feedback.

[broesler]

I like this idea... but should these vim variables be buffer-local so the user can set them per language? For example in iPython I use >>> !clear to clear the external shell screen, but that may vary on other interpreters.

[tinmarino]

Yes it would be better as buffer local. More coherent and extendable. Multi kernel support requires very little addition now but the global I've just put breaks that.

…

On Thu, Apr 9, 2020, 23:40 Bernard Roesler ***@***.***> wrote: I like this idea... but should these vim variables be buffer-local so the user can set them per language? For example in iPython I use >>> !clear to clear the external shell screen, but that may vary on other interpreters. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#25 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABOXDOSPGDYNN7ADNNHY4ADRL2BJNANCNFSM4MDAGPGQ> .

[tinmarino]

I changed it, updated the doc and the comment above:

autocmd FileType python let b:jupyter_exec_before = 'clear-screen'

[jagjordi]

I'm not sure if I am doing something wrong but after running git chechout dev the plugin commands are not recognized in vim

[tinmarino]

1. :set filetype returns python ? ?
2. :JupyterConnect exists ?

[jagjordi]

1. Yes
2. No

What type of log shoudl I provide to debug this?
Just to clarify, everything works fine in master branch

[tinmarino]

What type of log shoudl I provide to debug this?

Very good question, There is no protocol yet. The trust is in the code. You can start with loading order in this wiki or trust my 1,2,3.

1 plugin

1.5: :echo g:loaded_jupyter_vim -> 1 ? I think it's ok for you. If not the plugin is not loaded
1.6: :echo b:jupyter_kernel_type -> python

2 autoload

2.1: :call jupyter#load#MakeStandardCommands() there you should have the command

3 python

3.1/ :python3 print(_jupyter_session) -> something like <jupyter_vim.JupyterVimSession object at 0x7f15cd4e5650>

[tinmarino]

@jagjordi did you fix it ? How ? I added a troobleshoot wiki

[tinmarino]

The new command is JConnect (d4d85de) nobody likes typing especially vim users (good job @broesler)

[jagjordi]

Sorry for the late response. Now It works fine, the problem was that I was using JupyterConnect still!!! Thank you! I guess the issue can be closed now :)