Make the streak-mode coexist with the default mode

[bohrshaw]

Instead of overriding the default mode with let g:sneak#streak = 1, I prefer to be able to use the streak-mode along with the normal mode. I would like to use mappings starting with <leader>s in the streak-mode.

[justinmk]

Try this (with g:sneak#streak = 0):

nmap <leader>s <Plug>SneakStreak

I haven't tested this and it isn't documented yet, so I'll use this issue as a reminder to do so.

Also, what particular annoyances did you find with the "overriding" behavior? The goal is to remove as many of those annoyances as possible.

Thanks for the report!

[bohrshaw]

I haven't found any annoyance and I'm quite thankful for such a beautiful work.
Once I was inspired by "vim-seek", but didn't have the time to improve it further. But now with this sneak plugin, I find motions in Vim is almost complete.
However the stock fFtT motions are now less attractive to me. So I'm wondering if these motions will also be improved in future versions of 'vim-sneak'. I suppose these motions will be just like sS except that they are inline and accept only one character.

[bohrshaw]

I notice sc<CR> move the cursor to a single character c. I think this is f's job, which is currently not done perfectly(alternative characters should better be highlighted). So I urge to improve fFtT and let sc<CR> jump to the c at the end of a line. Similarly, s<CR>c can also jump to c at the beginning of a line, while s<CR> to repeat the previous jump can be replaced by s<BS>.
In the meanwhile, I see that <CR> is a non-printable character, so I have doubts if this is possible.

[justinmk]

@bohrshaw Thanks for the kind words!

fFtT motions are now less attractive to me. So I'm wondering if these motions will also be improved in future versions of 'vim-sneak'. I suppose these motions will be just like sS except that they are inline and accept only one character.

issue #24, right? That's the next thing on my list, stay tuned.

let sc jump to the c at the end of a line

I thought about that, I suppose people would also want <tab>, right? I think when issue #24 is addressed, maybe 2-character sneak should change its behavior...

[justinmk]

@bohrshaw For fFtT try these new commands:

    nnoremap f :Sneak!         1<cr>
    nnoremap F :SneakBackward! 1<cr>
    xnoremap f :<c-u>SneakV!         1<cr>
    xnoremap F :<c-u>SneakVBackward! 1<cr>

I'm going to close this issue, since I assume all your questions have been answered, except the one I moved here: #43

[bohrshaw]

If there's an option setting fFtT to sneak within a single line, that would be far better for me.

As it's often more preferable to seek two characters when jumping across lines(or using easymotion/streak-mode). And it's not neat for jumping within one line like this.

[justinmk]

If there's an option setting fFtT to sneak within a single line,

Why not just use regular fFtT?

[bohrshaw]

I like the matching characters highlighted ahead, so I'm not blindly repeating with ; or ,, especially when there're several matches in a line.

I know this's is a small enhancement which may be trivial to many others. But I would appreciate it as I'm using fFtT very often.

[justinmk]

Ok, I'm confused, because I thought you wanted it so that the search is restricted to a single line. But then this sentence makes it sound like you want it to behave multi-line:

especially when there're several matches in a line.

If that's the case, then you can set up these mappings and f/F will use single-character sneak. Is there something I'm missing?

[bohrshaw]

Sorry for the confusion. (I am still on the early stage learning English and its expression.)

I do mean "fFtT(with highlighting) only in the current single line". However I now realise this is really trivial in many situations. But fFtT in a range of the whole page is certainly not my way.

So I re-propose to provide an option to limit single-character-jumping within just two lines.

[justinmk]

No worries, your English is fine. I think the feature request though is a bit out-of-scope for the plugin. It is not well-defined, so it will be confusing to users who just want consistent behavior.