You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 15, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Aug 15, 2026. It is now read-only.
Your options are currently kind of limited for debugging vim plugin code running under vroom. You can use --interactive mode and purposefully trigger failures to inspect vim state, and of course you can use print statement debugging. Using :breakadd func FuncName inside vroom files doesn't seem to work as expected, probably due to all the arbitrary delay times.
It would be great to have more convenient support for entering interactive debugging. This might mean detecting vim is in interactive debugging mode so that you could use :breakadd normally, and maybe a vroom directive to pause vim for troubleshooting (or maybe special-case :breakadd here in vroom files).
Activity