On Wed, Aug 20, 2014 at 2:52 AM, Fidel N wrote:
> Its true, in general jumps just one page, but if the body pane is a bit
> bigger / smaller than X full lines (ie total length is, for instance, 12'5
> lines), it jumps one line more than desirable, so you have to go back to
> read it.
You are righ
The problem has been fixed although still not sure of the underlying cause:
I upgraded to PyQt version 4.8.6 from 4.8.5 and the issue of a colon being
recognized as a semicolon in normal mode disappeared and vim-mode is now
working fine for me. I can't find detailed release notes for PyQt so not
Excellent.
On Wednesday, August 20, 2014 2:38:50 PM UTC+3, Edward K. Ream wrote:
>
> In an earlier post I said:
>
> QQQ
> Strictly speaking, tab cycling doesn't have to be disabled for all colon
> commands. One could imaging a list of commands that use tab to complete
> file names. Otoh, mainta
On Wednesday, August 20, 2014 6:38:50 AM UTC-5, Edward K. Ream wrote:
> P.S. Here is the flattened form of the class that handles the :tabnew
command (does not require vim-mode). In particular, note that the __call__
and tab_callback methods are trivial. This is the way it is written in The
In an earlier post I said:
QQQ
Strictly speaking, tab cycling doesn't have to be disabled for all colon
commands. One could imaging a list of commands that use tab to complete
file names. Otoh, maintaining that list would be clumsy, and it would add
still more special cases to ga.do_tab.
QQQ
