Idan Arye

Please add an entry to `doc/vebugger.txt`.

I imagine the syntax as something like this: ```rust fn edit_system_with_exclusive_mode( mut ui: ResMut, mut edit: YoleckEdit, mut exclusive: YoleckExclusive, // this captures the system (like `YoleckMarking` does) uuid_query: Query,...

Alternatively, maybe this can be combined with #20's mechanism? ```rust fn edit_system_that_initiates_the_exclusive_mode( mut ui: ResMut, mut edit: YoleckEdit, mut exclusive: YoleckExclusive, uuid_query: Query, ) { let Ok(_) = edit.get_single_mut() else...

I'm afraid I'm going to have to reject this one. Vim's repeat command is for repeating text changes - the common use is to do a change, move the cursor...

repeat.vim works by storing the last repeatable command's info in global variables. You can probably do the same with your own global(or script) variables, and make you own keymapable command...

Maybe I explained myself wrong. I didn't say not to register the last vebugger command in some hook inside the plugin - what I said is not to register them...

What is `VBGpostcmd`?

If you are making an extension hook, make it right. The main users of extension hooks are not human Vim users, but other plugins that extend Vebugger. But such plugins...

@rdnetto I've pushed it to `develop`. Most user commands(except for starting/killing the debugger and altering the breakpoints) now go through `vebugger#userAction`, which registers the action in the active debugger object...

Well, the idea was that even if an event listener throws, the user action will still happen(because I'd like to avoid breaking the main functionality of the plugin just because...