@@ -18,7 +18,7 @@ Vim, like what you get with: ``object?<enter>`` and ``object.<tab>`` in
1818IPython.
1919
2020The big change from previous versions of ``ipy.vim `` is that it no longer
21- the old requires the brittle ipy_vimserver.py instantiation, and since
21+ the old requires the brittle `` ipy_vimserver.py `` instantiation, and since
2222it uses just vim and python, it is platform independent (i.e. should work
2323even on windows, unlike the previous \* nix only solution). The requirements
2424are IPython 0.11+ with zeromq capabilities, vim compiled with +python.
@@ -114,6 +114,7 @@ If at any later time you wish to bring this shell up, including if you've set
114114Options
115115-------
116116You can change these at the top of the ipy.vim::
117+
117118 reselect = False # reselect lines after sending from Visual mode
118119 show_execution_count = True # wait to get numbers for In[43]: feedback?
119120 monitor_subchannel = True # update vim-ipython 'shell' on every send?
@@ -131,13 +132,27 @@ The ipdb integration is not yet re-implemented.
131132
132133There were some unicode errors, but they should all be fixed now.
133134
134- If you're running inside ``screen ``, read about the ``<CTRL-S> `` issue here _,
135+ If you're running inside ``screen ``, read about the ``<CTRL-S> `` issue
136+ `here <http://munkymorgy.blogspot.com/2008/07/screen-ctrl-s-bug.html >`_,
135137and add this line to your ``.bashrc `` to fix it::
138+
136139 stty stop undef # to unmap ctrl-s
137140
138- _here: http://munkymorgy.blogspot.com/2008/07/screen-ctrl-s-bug.html
141+ In vim, if you're getting
142+ ``ImportError: No module named IPython.zmq.blockingkernelmanager ``
143+ but are able to import it in regular python, *either * your
144+ ``sys.path `` in vim differs from the ``sys.path `` in regular python. Try
145+ running these two lines, and comparing their output files:
146+ ``vim -c 'py import vim, sys; vim.current.buffer.append(sys.path)' -c':wq vim_syspath' ``
147+ and
148+ ``python -c "import sys; f=file('python_syspath','w'); f.write('\n'.join(sys.path)); f.close()" ``
149+ *or * your vim is compiled
150+ against a different python than you are launching (see if there's a difference
151+ between ``:py import os; print os.__file__ `` in vim with the same commands in
152+ python).
139153
140154------
141155Thanks
142156------
143- @MinRK for guiding me through the IPython kernel manager protocol.
157+ * @MinRK for guiding me through the IPython kernel manager protocol.
158+ * @nakamuray and @tcheneau for reporting and providing a fix for when vim is compiled without a gui
0 commit comments