Open ts826848 opened 6 years ago
Actually, it seems it is the desired behavior, see this comment bloc: https://github.com/haya14busa/is.vim/blob/master/autoload/is.vim#L31 However, the documentation is imho incoherent with that =/
The good news is, you can have the behavior of C-{g,t} on C-{j,k} like so:
let g:is#do_default_mappings = 0
cnoremap <C-j> <C-g>
cnoremap <C-k> <C-t>
My understanding of the difference between
C-j
/C-k
from this plugin and the built-inC-g
/C-t
is that the built-in ones advance the cursor from match to match, while the ones from this plugin advance screen-by-screen, moving the cursor to a suitable location as necessary. Am I understanding this correctly?If
C-j
/C-k
are supposed to scroll screen-by-screen, I don't appear to get the same kind of scrolling as in the recordings in the repo. When I hitC-j
, instead of jumping up/down a screen, the cursor starts advancing to the next match until the screen has scrolled down some amount, at which point it starts jumping to the previous match until some point. The net effect is moving screen-by-screen, but it doesn't really seem right.An example screen recording can be found here
The .vimrc used for the example:
Output of
vim --version
: