How to change the auto-jumped cursor color?

[kohane27]

Hello @ggandor. Hope you're doing well. Thank you for creating flit.nvim; it complements leap.nvim very nicely.

Description

if vim.v.count == 0 and not (kwargs.unlabeled and vim.fn.mode(1):match("o")) then
^
cursor

2. press fa to forward search all occurrences of a

if vim.v.count == 0 and not (kwargs.unlabeled and vim.fn.mode(1):match("o")) then
^                   ^
old cursor      auto jumped cursor

4. Two white-background cursor shows up

I find it a bit disorienting because I see two same white cursors, without knowing which cursor I'm currently on. Of course, if I think about it, I'll know which cursor I'm on, but it takes a bit of mental overhead. I think two same white cursors introduces a bit of visual clutter and I'm looking for a way to change the auto-jumped cursor color (i.e., the second cursor color).

What I've done

I've looked into :h leap-highlight and found the following color groups: LeapMatch, LeapLabelPrimary, LeapLabelSecondary, LeapLabelSelected, LeapBackdrop. I've tried changing each value but none targets the auto-jumped first cursor.

Any input is much appreciated. Thank you again for revolutionizing my navigation in Neovim.

[ggandor]

Sometimes, I find it a bit disorienting because I see two same white-background cursors, without knowing which cursor I'm on

Sure, this is a bug introduced by 0.8 (see #3 and ggandor/leap.nvim#70). I don't want to expose a LeapCursor group solely as a workaround, let's just live with this until the core issue is fixed.

[kohane27]

Hello @ggandor , thank you for getting back to me. I really appreciate it. I understand and sorry for not searching through the issues more thoroughly. I'll keep an eye on this upstream issue and update everyone if there's progress upstream. Thank you again:)

[woshichuanqilz]

Sometimes, I find it a bit disorienting because I see two same white-background cursors, without knowing which cursor I'm on

Sure, this is a bug introduced by 0.8 (see #3 and ggandor/leap.nvim#70). I don't want to expose a LeapCursor group solely as a workaround, let's just live with this until the core issue is fixed.

Not push. I just want to know when the issue will be solved. Because I try to solve it the whole noon, go through all the help file about config and highlight until I see this issue 😄 .

I want to use flit but the same cursor color for the first two positions really confuse me. I will use the original f for now. And use flit when this issue be fixed. Thank you 😄