György Andorka

> looks like the dot-repeat enters d~@ý, at least it's displayed in the bottom right. Yep. It is also interesting that this only happens after _one_ dot-repeat - that is,...

> I only get as far as dta -> dot-repeat, before nvim seizes up To be clear: you experience this problem _without_ undoing the change first?

> Tested some more today, seems I did not read the README properly and never added the tpope/vim-repeat dependency Well... :D > Have you considered changing the dot-repeat implementation as...

> Which should be relatively straight forward, but my non-existent experience with fennel (and lisp in general) is making it a bit harder to read the code and figure out...

Okay, thanks! Just a quick glance: First, let's leave Telescope out of this PR completely, as this refactor is much more general, and limit additions to the documentation to the...

On the todo list!

This is exactly what lightspeed's [shortcuts](https://github.com/ggandor/lightspeed.nvim#shortcuts) do. It's even better than what you described, because the remaining hints don't change when refreshing, so you don't _have to_ pause after the...

Thinking about your specific proposal a bit more, I don't see much point in it - maybe I don't fully understand it. This just collapses 1-char mode and 2-char mode...

@jakubbortlik The input is saved in flit's `state` table, which is currently private, so just return that from the module, if you want a less hacky hack: https://github.com/ggandor/flit.nvim/blob/498b3a4864e697f1ed1145e518c4c78c776c55d8/lua/flit.lua#L3

> I would like to just define: ``` require('flit').setup { keys = { f = 'f', F = 'F'}, } ``` This already works, you're free to leave out those...