Interaction with minibufexpl

[smutch]

If minibufexpl is loaded then when the "Ctrl-s" command is used (in both command and insert modes) the minibufexpl window is selected.

This is frustrating as it is necessary to manually re-select the window of the file being edited after sending each command.

[ivanov]

Thanks for the report, but I am unable to replicate this on
vim-ipython trunk using 6.3.2 version of minibufexpl.vim from
here:
http://www.vim.org/scripts/script.php?script_id=159

are you using a different one?

[ivanov]

ok, i think you must be using the one on @fholgado github, as I see the issue you describe there.

You can get the desired behavior with :let g:miniBufExplorerAutoUpdate=0 - but I'm not sure how that affects your usage of minibufexplorer. The problem is that when you hit ctrl-s, vim-ipython will open up its shell, if it's not already open, switch to it, update it with the input and output of ipython, and then switch back to the previous window. When this version of miniBufExplorer auto-updates, it does so just in the middle of the vim-ipython action, so the previous window becomes the minibuf, not the one we sent things from.

I think that there's a different way to get the desired effect that the new minibuf is train to attain: because as-is - ctrl-w p is "broken" in minibuf if AutoUpdate is enabled - so I consider this a bug/feature of minibufexpl, not vim-ipython

[smutch]

Ok.

Thanks for the quick response. From what you say, I definitely agree that this in fact a minibufexpl bug.

Thanks again!

[ivanov]

glad to help. FWIW and for posterity - this is a known issue in this version of minibufexpl and listed as their bugs fholgado/minibufexpl.vim#3, fholgado/minibufexpl.vim#7, fholgado/minibufexpl.vim#12, and fholgado/minibufexpl.vim#21

[ivanov]

just an update, it looks like this issue has been resolved in fholgado/minibufexpl.vim#3

[smutch]

Thanks for the update. I gave up minibufexpl in favour of vim-ipython so I'll give it a go again. :)

On Thursday, 1 March 2012 at 9:19 PM, Paul Ivanov wrote:

just an update, it looks like this issue has been resolved in fholgado/minibufexpl.vim#3

---

Reply to this email directly or view it on GitHub:
#7 (comment)