Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

when target of an f operation is ( or ) cursor doesn't jump to it (or if it does it's invisible) #44

Open
alexandreroberts opened this issue Dec 15, 2023 · 3 comments

Comments

@alexandreroberts
Copy link

alexandreroberts commented Dec 15, 2023

When I type f( the cursor does not appear to jump to the next (. But it clearly has because its pair is highlighted. E.g., if the cursor is on the first column in this line

word word (lkjsdf)

and then I type f(, the highlighting only changes for the ), not for the (, because I am using a package that highlights matching pairs. In any case, the ( should be highlighted to show that the cursor has arrived.

Perhaps this is related to this leap issue?

@ggandor
Copy link
Owner

ggandor commented Feb 2, 2024

Perhaps this is related to ggandor/leap.nvim#70?

Yep, might be related. So it's not a problem with the MatchParen highlight, if you just move the cursor to (, it is visible, right?

@alexandreroberts
Copy link
Author

Yes, that's right: when I simply move the cursor to (, in this case by typing ww, it is highlighted as normally (and also its matching paren is highlighted) -- exactly the expected behavior.

I should add that the issue seems to be restricted to whatever mode I'm in while using flit's f, where all the possible targets are marked. I say this because in the above example (word word (lkjsdf)), if I type f(<esc>, then the expected highlighting reappears, as if I had moved there with ww. So the problem exists only between the time I enter flit's f mode (by typing f() and the time I exit that mode, in this case by entering normal mode with the escape key.

@alexandreroberts
Copy link
Author

I have another observation to add: this problem takes place when flit's target is ( or {, but not when the target is [.

Does that help narrow down what is causing the problem?

(By the way, I just updated to Neovim 0.9.5, and the problem persists.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants