Hi,
> I am wondering how to debug a vim plugin (for example, the following
> one) in an efficient way.
>
> [...]
>
> Does anybody have any tips on how to debugging vim plugins? Thanks.
In my lh-vim-lib [1] library plugin I provide two sets of tools
- log functions [2] that can fill the qf window with the log messages automatically -- other logging frameworks fail to automatically link to the line where the log is emitted
- assert functions [3] for doing some design by contract. They permit to fail fast in case of unexpected value detected / dump the current callstack / start the debugger
It also provides a function that decodes displayed callstacks on error [4]
I also use a unit test framework [5] for unit testing functions.
[1] https://github.com/LucHermitte/lh-vim-lib
[2] https://github.com/LucHermitte/lh-vim-lib/blob/master/doc/Log.md
[3] https://github.com/LucHermitte/lh-vim-lib/blob/master/doc/DbC.md
[4] https://github.com/LucHermitte/lh-vim-lib/blob/master/doc/Callstack.md#lhexceptionsay_what
[5] https://github.com/LucHermitte/vim-UT
HTH,
--
Luc Hermitte
--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment