Skip to content
This repository has been archived by the owner on Sep 5, 2024. It is now read-only.

Can't use hop command in neovim #220

Closed
coderj001 opened this issue Jan 26, 2022 · 10 comments
Closed

Can't use hop command in neovim #220

coderj001 opened this issue Jan 26, 2022 · 10 comments

Comments

@coderj001
Copy link

image

@jyyyeung
Copy link

same issue here

@jyyyeung
Copy link

when using :HopChar1 and typing any letter, no hint shows up and sometimes all syntax highlighting on the file disappeared.
image

@curist
Copy link

curist commented Jan 29, 2022

Got the same issue using v1 branch with neovim v0.7.0; but latest version of hop.nvim works.
Relevant fix is in commit b33e02f, which isn't released yet.

@coderj001 coderj001 changed the title Can use hop command in neovim Can't use hop command in neovim Jan 29, 2022
@coderj001
Copy link
Author

Well i have switch to easymotion, as i cannot config hop.

@hadronized
Copy link
Owner

I’m going to have a look at this problem tonight or tomorrow, thanks for noticing.

@coderj001 coderj001 reopened this Feb 8, 2022
@dominicmason555
Copy link

I think this is the same issue I was having in #217, so far I had downgraded to Neovim v0.6.1 which fixed the issue, although now I think the problem was I had copied the following line in the installation with packer instructions from the README:

  branch = 'v1', -- optional but strongly recommended

since this branch does not contain the fix @curist mentioned, removing this line may fix the issue

@hadronized
Copy link
Owner

Yeah, I haven’t made a v1 release for a while. The thing is, if you are using the stable neovim, you shouldn’t have issues. If you do, then something is wrong with the code that assumes set_hint_extmarks expects a number. I’m fixing this today.

@hadronized
Copy link
Owner

My neovim Treesitter parser for Lua is completely broken; I’ll try fixing that first though.

@dominicmason555
Copy link

By removing the line about pinning the v1 branch I've got it working again in the latest nightly, but yeah v1 did still work with the stable neovim release 0.6.1

@hadronized
Copy link
Owner

This is now fixed. Sorry for the long delay, my life and OSS didn’t really cross paths lately.

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

No branches or pull requests

5 participants