György Andorka

@CaetanoBorges This repo is licensed under https://creativecommons.org/licenses/by/4.0/ - that means you are free to do so, just add a note stating "this is a Portuguese translation of X", with a...

A totally wild guess, maybe a misfire, but we've had a similar issue [here](https://github.com/ggandor/lightspeed.nvim/issues/7): skimming the codebase, I see that `feedkeys` is indeed called in a bunch of places, maybe...

Wait a minute, actually, I cannot reproduce this (both vanilla Vim and Nvim 0.5.0 execute the macro correctly).

Recorded the macro, checked `:reg`, it's `eldf(i: [^[^` indeed, replayed on the original line, but works flawlessly, with targets.vim active... Mysterious :) Edit: Now I could reproduce this, but with...

I start with case 2, because that is simpler: if the label is offscreen, that is a bug (I cannot reproduce though). You should see `hi[label1][label2]`, or `hih[label]` (if the...

It just occurred to me that a plugin like your iswap.nvim is the exact use case for Leap's multiselect mode. The very concept is that instead of having to reinvent...

> would you like me to file a bug report for the second case? Sure, thanks. > I'm not sure my plugin, which isn't published yet, is a good fit...

No, that is a bug (and I can reproduce). What's interesting is that lightspeed works fine, so it's probably some refactoring I did. Edit: fixed by 054456aa7fa6ddbee23b6ee6d50ad9086c9d78cc.

Yes, I'm noticing the same issue with certain colorschemes. No idea about the cause, we simply use the `Cursor` highlight group. Hopefully this whole virtual cursor hack will soon(er or...

Oh, that explains it. Of course themes should define `Cursor`. (Note: Those other groups with "Cursor" in their names aren't related to the cursor highlight, they are for highlighting the...