Tony Mechelynck wrote:
On Mon, Dec 10, 2018 at 3:55 PM Peng Yu <[email protected]> wrote:
Hi,
I am wondering how to debug a vim plugin (for example, the following
one) in an efficient way.
https://github.com/Clavelito/indent-sh.vim/blob/master/indent/sh.vim
The main difficulty that I see is that a vim plugin is different from
a typical program is that in a typical programming language one can
easily isolate a piece of code and insert print statements. But in a
vim plugin, since it causes some effects in the code shown in vim, I
am not sure how a print statement can help much.
Also, in a regular programming language, one can run a function with
different parameters, then check its behavior. But a vim plugin is
just a whole piece of code, it is not clear how to run a piece of code
in an isolated environment to inspect its behavior.
Does anybody have any tips on how to debugging vim plugins? Thanks.
--
Regards,
Peng
Debugging Vim-script language is Dr. Chip's province; he even wrote a
script to help debug other scripts. You may already check if
http://www.drchip.org/astronaut/vim/#DECHO helps you, otherwise I'm
adding Dr. Chip as Cc in case he might have other helpful information
for you.
Best regards,
Tony.
Hello:
Decho.vim would be my suggestion, too. Decho provides several ways to
help you get your debugging information out; a separate window on the
current tab, a separate tab, via vim's messages facility, and to a
remote vim. The latter provides the most isolation of debugging output
capture from effects on the script's display.
Regards,
Chip Campbell
--
--
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
