Add a screencast using byzanz

[albfan]

A picture (video) is worth a thousand words.

Create a screencast using two gvim instances or better a tmux session.

https://aur.archlinux.org/packages/byzanz/

[PhilRunninger]

I just came across this plugin. I've been looking for something like this for awhile. I'm having some learning curve issues that I need to work though, and a screencast would be great.

[albfan]

Sure I will create one where you can see:

• Breakpoints
• Step in/out, continue
• Moving around stacktrace
• Locals
• Evaluate expressions

Bump this in a week if I forgot for a while

[hrai]

Sure I will create one where you can see:

* Breakpoints

* Step in/out, continue

* Moving around stacktrace

* Locals

* Evaluate expressions

Bump this in a week if I forgot for a while

This would be great. I couldn't follow through the instructions properly to get it working.

[albfan]

Here you can see a debug session for https://github.com/albfan/ag.vim, showing

• start vim in servermode (Foo)
• connect from other vim as client to debug BPRemoteServ
• execute some commands (vim dynamic load)
• Refreshing available commands on vim client BPRefresh
• Navigate to function
• Set breakpoint
• Run command on vim server again
• Show where we are in vim client (f7 or BPDWhere)
• Next command on client BPDNext
• Show stacktrace BPDBacktrace on client and move around
• Show Locals BPDLocals
• Evaluate expressions BPDEvaluate

Maybe is a good idea to do it on an ascii capture service like https://asciinema.org/ or add Keystrokes and mouse pointer to the video. In github only gif can be added. Just let me know if you get blocked with anything.

If it gets polished, maybe we can add to wiki or similar

[PhilRunninger]

After a quick glance, I'd say this looks good. I'll have to study it more when I have time to do so. You're right that capturing keystrokes (especially Fn keys) would be a big help.

[hrai]

@albfan How did you add the breakpoint on the right window?

Also, if I'm executing a function on the server that I'm debugging on the right window, do I need to execute the function as debug <function_name>? Or simply calling the function/command will intercept the execution by the debugger?

ASCIIinema would definitely be easier to view+reference in questions.

Also, you wouldn't have to wait for a while to get to the point where you were at.

[albfan]

Check documentation:

:help breakpts

https://github.com/albfan/vim-breakpts/blob/master/doc/breakpts.txt#L313

There's a general mapping summary here:

https://github.com/albfan/vim-breakpts/blob/master/doc/breakpts.txt#L206

F9 or :BPToggle will set a breakpoint so when you run your command it will stop there. Then you need to call F7 or :BPDWhere because there's no event or similar so vim client will not move to that stopped line on its own. (Maybe someone can set a background task for that now we have async methods)

[hrai]

I got it working. Need to play around a little bit. Thanks for your help 😄