code is sent to the ipython console but not run

[Alan-Manning]

Hello,

I have got this working as i want it in terms of splits and everything but i cant get the code i send to the IPython colsole i have to run. I send it and then it just sits there and i have to switch to the split and then go into instert mode to press enter and then tab back out to the python file i was in before. Im pretty sure this is not intended. Anybody know why this might be happening?

I have posted a pic of the setup below.

Untitled.video.-.Made.with.Clipchamp.mp4

Any help appreciated.

Thank you

• Alan Manning

[PyDataBlog]

+1 I have the same issue here

[Alan-Manning]

+1 I have the same issue here

found that there is a plugin called toggle term and you can set up a keymap for ipython console. This also has commands to sent lines, visual selection etc to the terminal. here is a video showing it with the setup, he uses python but can easily be changed to ipython, https://youtu.be/5OD-7h7gzxU.
The docs for toggle term show the ipython console example there with sending line etc to it, https://github.com/akinsho/toggleterm.nvim#termselect.

Hope this helps.

[PyDataBlog]

+1 I have the same issue here

found that there is a plugin called toggle term and you can set up a keymap for ipython console. This also has commands to sent lines, visual selection etc to the terminal. here is a video showing it with the setup, he uses python but can easily be changed to ipython, https://youtu.be/5OD-7h7gzxU. The docs for toggle term show the ipython console example there with sending line etc to it, https://github.com/akinsho/toggleterm.nvim#termselect.

Hope this helps.

Thanks! I will check it out. It's a shame this issue is holding me back from using this plugin.

[g-plus-theworld]

Hiya,

I had this issue and I found a workaround that is suitable for me. Until the ipython issue is fixed, you can switch to use the python executable instead. Like instead of typing "ipython" to the terminal you will get a REPL that looks like as if you have entered "python" or "python3". Here is what I did:

I use lazy as my package manager on windows so my plugins are downloaded to this folder:
C:/Users/"myusername"/AppData/Local/nvim-data/lazy/

Here I opened this file:
C:/Users/"myusername"/AppData/Local/nvim-data/lazy/iron.nvim/lua/iron/fts/python.lua

And edited line 31 (for me that is), to point ipython to the python executable.

Now when I open IronRepl It opens a "python" terminal and I can send code to it and it will execute.

Hope this helps and you can keep using the great plugin! :)

[PyDataBlog]

Hiya,

I had this issue and I found a workaround that is suitable for me. Until the ipython issue is fixed, you can switch to use the python executable instead. Like instead of typing "ipython" to the terminal you will get a REPL that looks like as if you have entered "python" or "python3". Here is what I did:

I use lazy as my package manager on windows so my plugins are downloaded to this folder:

C:/Users/"myusername"/AppData/Local/nvim-data/lazy/

Here I opened this file:

C:/Users/"myusername"/AppData/Local/nvim-data/lazy/iron.nvim/lua/iron/fts/python.lua

And edited line 31 (for me that is), to point ipython to the python executable.

Now when I open IronRepl It opens a "python" terminal and I can send code to it and it will execute.

Hope this helps and you can keep using the great plugin! :)

I also switched to Toggle term. Exactly what I needed.

[nickeisenberg]

@g-plus-theworld @PyDataBlog @Alan-Manning Are you guys still using the pluggin and if so are you having the same problem. I am unable to reproduce the error you guys are having.

[Alan-Manning]

@g-plus-theworld @PyDataBlog @Alan-Manning Are you guys still using the pluggin and if so are you having the same problem. I am unable to reproduce the error you guys are having.

i am not using this anymore. just using toggle term and launching ipython console through that. I think that there may be some ipython settings for smart return/ make a new line and not run if command is incomplete, i cant recall what its called. i have had some issues with other setups ive tinkered with because of this and might not be specifically related to this plugin, However if you do find out what causes this, id imagine a section in the readme about that might be usefull to others

[nickeisenberg]

@Alan-Manning Hey how were you sending code to the terminal. where you using visual_send?

[PyDataBlog]

@Alan-Manning Hey how were you sending code to the terminal. where you using visual_send?

Use toggleterm plugin

[nickeisenberg]

@PyDataBlog mainly asking to see if the problem can be solved.

[PyDataBlog]

@PyDataBlog mainly asking to see if the problem can be solved.

I switched plugins so can't verify

[roteiro]

@nickeisenberg I still have the issues described in this thread. My environment:

• Windows 10 (Powershell 5.1.19041.429),
• IPython 8.24.0
• Windows Terminal 1.19.10821.0.

The behaviour seems to be the same, regardless if I use iron or toggleterm. I didn't do detailed tests with iron yet, but with toggleterm, the code is not executed regardless whether I use visual send or send current line.
If I launch with ipython --simple-prompt, the code is executed correctly.
@PyDataBlog did you do any specific configuration for toggleterm to get direct execution or did it work out of the box?

I'd be happy to see this issue resolved and can provide further input if needed.

[nickeisenberg]

Hey @roteiro, I think I fixed the issue. If you have time, could you do me a favor and test it on your end? Can you use your package manager to install my fork of iron.nvim and see if the changes fix the ipython issue you were having. My fork is located at nickeisenberg/iron.nvim, this fork is exactly the same as the original, so all you need to do is replace Vigemus/iron.nvim with nickeisenberg/iron.nvim in your package manager and the rest of your setup can stay the same. I tested the changes on my end with windows11 and it seemed to be working. I think at the moment, windows will only work with ipython, at least that has been my experience when using powershell.

[roteiro]

@nickeisenberg great, it works! I tested send line, send file and visual send. As I understood from your commit, you deferring the final cr call. Could you elaborate on the root of the problem?

€: If I send a file with many lines, such that the sending process takes quite long, the issue is still there. Probably because the sending takes longer than the added deferall?

[nickeisenberg]

@roteiro How many lines are you trying to send? I am unsure what the real issue is because it doesnt occur on linux or mac. I can try and mess around with it some more.

E: I just tested it and I see what you mean, I do not have this issue with windows + powershell + python, its only with ipython. In the meantime, an quick fix is to add the cr keymap to your setup. then <space><cr> will run the code that never ran in the ipython terminal.

return {
  "Vigemus/iron.nvim",
  config = function()
    local iron = require("iron.core")

    iron.setup {
        ...
      keymaps = {
         ...
        cr = "<space><cr>",
        ...
      },
    }
}

[roteiro]

jpalardy/vim-slime#297 (comment)
This issue sounds very related and the linked comment has a possible solution in vimscript