Closed mark2185 closed 1 year ago
Sorry for not getting around to this.
I believe this is due to a design choice of quick-scope. If I remember correctly the highlighting identifies characters to jump to to quickly get to other words in the line (and so it skips over targets in the current word).
Sorry for not getting around to this.
No worries, there are more important things than github issues :)
I believe this is due to a design choice of quick-scope.
That sounds reasonable. Thanks for clearing it up!
I've just come across something that contradicts this, though.
Your explanation does explain why the m
after the cursor isn't highlighted, but why isn't the m
in maybe
highlighted at all?
The example from above at least highlights the second t
, albeit in a secondary color since it's the second t.
This one might require me to read through the target selection more closely, but I think it is probably skipping the m
because the y
is a first order target to get to that word. Since that word already has a first order target we don't need to search for other targets to get us to that word.
In the earlier example the t
gets highlighted because it's a second order target (quick-scope doesn't consider beyond 2) and that word has no first order targets.
Does that help?
Alright, I'll take your word for it.
I guess I should just use what I get instead of trying to reason why I'm not getting what I want (even though what I want isn't the most useful so I should adjust my expectations)
Thanks once again! :)
Noticed it happening on this:
I put the cursor on e.g. the first
h
inhighlight
and trigger the quick-scope highlight and there are multiplet
s, the first one being in the same word, but only the second one gets highlighted.It's reproducible with this minimal
vimrc
:I tried different colorschemes, nothing changes, so I'm guessing it really doesn't change, not that it's just not visible.