Idan Arye

Not currently.

I just tried it on a Rust project with GDB and it just worked. As for LLDB, I had to run `:VBGcontinue` after launching the debugger - apparently it got...

OK, I tested that script, and `:VBGcontinue` has nothing to do with it - the reason I had to do it is that Vebugger automatically sets a breakpoint on `main`,...

VimPlug is weird like that - you need spaces inside the curly brackets: ```vim Plug 'idanarye/vim-vebugger', { 'branch': 'develop' } ```

@IngoHeimbach - mind taking a look?

You need to open the buffer before the crash - it does not show output from before it was opened.

After starting the vebugger, before the crash... try this: ```vim call vebugger#lldb#start('test.out',{'args':['hello','world']}) | VBGtoggleTerminalBuffer ```

Neovim may actually benefit from the async nature of it's job API, but from what I understand about Vim's new job API(I didn't actually try it - just read [the...

I've looked a bit more into Vim's new job API doc's, and it seems like I was wrong - it's also async.

There is always hope - but I can't promise when I'll have time to actually work on it. It'll be a great excuse to raise the minimal requirements to Vim8(/Neovim)...