You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You can see in the below screenshot that although my cursor is not actually on any word at all, Matchmaker is highlighting (underlining) the word closest to the cursor.
It's very strange that anything should be highlighted when I'm not focusing on anything. I find it much more of a distraction than it is helpful. Could we highlight words only when the cursor is truly on top of them? Or perhaps at least make this an option?
Thanks!
The text was updated successfully, but these errors were encountered:
I agree. The reason for this is we just use expand('<cword>') which is
interpreted as the word closest to the cursor. I could put in a check of
some kind to assert that the character under the cursor is a keyword
character.
You can see in the below screenshot that although my cursor is not
actually on any word at all, Matchmaker is highlighting (underlining) the
word closest to the cursor.
It's very strange that anything should be highlighted when I'm not
focusing on anything. I find it much more of a distraction than it is
helpful. Could we highlight words only when the cursor is truly on top of
them? Or perhaps at least make this an option?
Thanks!
—
Reply to this email directly or view it on GitHub #18.
You can see in the below screenshot that although my cursor is not actually on any word at all, Matchmaker is highlighting (underlining) the word closest to the cursor.
It's very strange that anything should be highlighted when I'm not focusing on anything. I find it much more of a distraction than it is helpful. Could we highlight words only when the cursor is truly on top of them? Or perhaps at least make this an option?
Thanks!
The text was updated successfully, but these errors were encountered: