KillTheMule

I'm on a pretty recent HEAD version. `:map ` shows "no mapping found". The keypresses do whatever the usually do in insert mode.

Ok, that gave it away, it's [this line](https://github.com/Vigemus/impromptu.nvim/commit/acdd34d479c1040cb74540148688178c46bb75de#diff-7a3265fcf07c684e0a601a45ef019357R229). Changing `~=` to `==` fixes it.

Ok, filter seems fine now, gonna try the config options now :) Should I keep asking here, or make new issues? There was a change in `ask`, namely the 2nd...

Thanks for the clarifications! An yeah, using your own HL groups is probably the most sensible thing anyways.

Ah, another question if you don't mind. What are your assumptions on the keys of the options in `ask`'s options? Seeing that the value is passed to the handler instead...

Aaannd an improvement idea: Using `` selects the next option in `filter`, but you can't scroll if the number of shown options is larger than the buffer size. That's a...

> ... and I think this calls up for setting a test infrastructure to avoid regressions. I once wrote a [blog post](https://github.com/KillTheMule/KillTheMule.github.io/blob/master/test_plugins_from_neovim.md) about that. If you're interested, I can set...

> * check source, not output I'd have to disagree here, seeing how many scripting facilities typst has. Can one be really sure what the final output strings are before...

I've started investigating this, and it's definitely entered Heisenterritory for me... For reproduction, see https://github.com/KillTheMule/reqbug. Check out the neovim submodule, build with the [included script](https://github.com/KillTheMule/reqbug/blob/main/build_nvim) (just so we have a...

I'm kind of a loss for words :D I've applied https://github.com/neovim/neovim/pull/25494 to neovim, and the following happens: - I can still trigger the crash - ~~When *not* crashing, the log...