Ben Jackson

I still don't fully understand what feature this is requesting.

Wait is the logic: * If there are `mods`, use "always split" * If there are no mods, use "split or current buffer" ? if so I think I can...

Test for legacy vim script too: ```viml py3

And to be clear, bind evaluations work - i.e. assignment to dict members, etc. works as-if using bindeval: ``` vim9script var dnew = { 'one': 1, 'two': 2, 'old': 0...

@mergify refresh

OK sure, no rush.

I have no clue what you are asking for.

To summarise the use-case for vimspector (https://github.com/puremourning/vimspector/pull/316): * Vimspector is a debugging UI for vim (supporting many different languages) * It currently uses `ballooneval`/`balloon_show()` etc. to support mouse-hover on an...

on reflection, for our case a `popup_filter_normal` would work, which would just be a built-in filter that does "most" of the normal mode commands for navigation and prevents bad things...

Yep, agree. I was thinking with the normal filter to do something like: ```viml function! MyFilter( char ) if a:char === "\" " expand (asynchronously) if vimspector#ExpandVariable( ... ) return...