Evgeni Chasnovski

I've recently written a [mini.starter](https://github.com/echasnovski/mini.nvim#ministarter) - module of [mini.nvim](https://github.com/echasnovski/mini.nvim) plugin. By default it displays sessions (if 'mini.sessions' is set up), MRU files and some actions, but all items are fully...

After some banging against the wall, I believe I found the culprit of the problem. This was a result of 'hit-enter-prompt' triggered on `VimLeavePre` event. Try running on the test...

> So basically we only broke your custom stuff because VimLeavePre never run. My point was that it never ran before, but now it differs depending on Neovim version (which...

I've recently released [mini.ai](https://github.com/echasnovski/mini.nvim#miniai) - module of 'mini.nvim' for extending and creating `a`/`i` textobjects. This is basically an extended 'targets.vim', but in Lua and a bit different.

Hi again! Thanks so much for your enthusiasm! I usually prefer writing them on my own because of a joy I am getting while creating new API and functionality. However,...

> Just a heads up that the current implementation of `vim.on_key()` is not useable. It's what I initially looked at :) Interesting. Thanks for sharing! Is it because of "receive...

> The `on_key` calback only gets called **after** evaluating the mappings. And the keys are indeed the evaluated keys. > > What we would need to do it properly, is:...

Thanks for the issue! Unfortunately, this is how extmarks (which are used for displaying scope) work right now, to the best of my knowledge. This is a combination of two...

Thanks for kind words! And for opening an issue to discuss before actually making a PR. And for contribution suggestion. I am really not sure about this at the moment....

> Oh, didn't know about mini.ai; I just tried it and it meets my needs (and saves one keystroke), only I don't know why it is slower than the modified...