> Waking up this thread, just to say that this is still work in progress. I
> actually use it quite often for my own debugging, but I'm holding off on
> patches for now while vim9script develops. I think it makes logical sense
> for this all to happen after vim9script is mature.
>
> But as a teaser, I noticed that Bram added support for debugging vim9script
> statements yesterday, and so I've hooked that in to my prototype. So here's
> a demo of Vimspector debugging a simple vim9 script:
>
> https://asciinema.org/a/25SLL99WepcubhweLoQblz2Cg
>
> Lots more to do on this, but now the framework is in place.
I'm glad the Vim9 debugger features work for you. I plan to add the
possibility to inspect function arguments next. Not sure if I add more
now, it should be sufficient for basic debugging. Perhaps we need
to be able setting a breakpoint?
--
You can test a person's importance in the organization by asking how much RAM
his computer has. Anybody who knows the answer to that question is not a
decision-maker.
(Scott Adams - The Dilbert principle)
/// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\
/// \\\
\\\ sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_dev/202106151036.15FAa2hw1075908%40masaka.moolenaar.net.
