György Andorka

I think that issue has been fixed (see https://github.com/ggandor/leap.nvim/issues/108). Could you give a reproducible example?

I cannot reproduce, the plugin finds everything correctly even after using those fancy characters. Could you copy/paste the buffer content instead of screenshots, for a sanity check?

Closed by 847a740 (should work on stable versions too now).

> I'm assuming this is not the intended behavior? > the repeat keys still seem to be active even when you are no longer in the context of leaping. These...

Off-topic: what is the colorscheme? Looks nice :)

> I believe it will be solved by the repeat parameter hinted in https://github.com/ggandor/leap.nvim/issues/176 Nope, unrelated :)

> While this does seem to work for the most part, it unfortunately overwrites the default next_target and prev_target mappings... Here is a clean solution: ```lua local set_phase2_traversal_keys do --...

Also related: #65, #151, https://github.com/ggandor/leap-spooky.nvim/issues/11, https://github.com/ggandor/leap-spooky.nvim/pull/12

> Since https://github.com/mfussenegger/nvim-treehopper/issues/23 has there been any progress or thought on how to do the labelling for ranges rather than single position targets? Not really, this is very low priority...

> without complicating the internals of Leap *internals & interface > I think a first step could be adding `endpos` This feels very ad-hoc, I'd rather have a general `beacon`...