#vdebug

[x-yuri]

vdebug + python

$ curl 'http://downloads.activestate.com/Komodo/releases/archive/8.x/8.5.4/remotedebugging/Komodo-PythonRemoteDebugging-8.5.4-86985-linux-x86_64.tar.gz?_ga=2.213132828.928515719.1533909623-2080295309.1533909623' -o Komodo-PythonRemoteDebugging-8.5.4-86985-linux-x86_64.tar.gz $ tar xf Komodo-PythonRemoteDebugging-8.5.4-86985-linux-x86_64.tar.gz $ cd Komodo-PythonRemoteDebugging-8.5.4-86985-linux-x86_64 $ cp -r python3lib/dbgp . $ curl -L https://gist.githubusercontent.com/x-yuri/1ec2e2a67b5c2aae994668b7bde6fd4d/raw/854bcdd1ce2c3de856b89c4024a7b53c30fd7c67/client.py.patch -o dbgp/client.py.patch $ patch dbgp/client.py < dbgp/client.py.patch // the following patch allows to debug scripts that behave differently // depending on basename($0) (symlink) // e.g. ansible-playbook // or else it would think it's run as ansible $ curl -L https://gist.githubusercontent.com/x-yuri/1ec2e2a67b5c2aae994668b7bde6fd4d/raw/854bcdd1ce2c3de856b89c4024a7b53c30fd7c67/pydbgp.patch -o pydbgp.patch $ patch pydbgp < pydbgp.patch // <F5> in vim $ path/to/pypdbg -d localhost:9000 /path/to/script # 9001 in my case

[sheilalmartinia]

Debugging WordPress with Local by Flywheel, (neo)vim, and xdebug

Introduction Local by Flywheel is a popular tool for getting quick and reliable WordPress installations running on your computer. One of its lesser-known features is the inclusion of xdebug support. xdebug is a PHP extension that allows for real-time debugging of PHP code. Today, we’re going to go over how to get both of these working together within vim to provide a powerful interface that allows for some successful debugging of WordPress. Prerequisites Firstly, this tutorial is intended for users of vim or neovim. If you aren’t familiar with how to use vi-like editors, but want to learn, I would recommend running vimtutor in your command line and learning how to move and work in vim before continuing with this post. Next, you’ll need Local by Flywheel. You can download it here. If you haven’t set up a site before with Local, it is pretty straightforward. You can find a guide for getting started on Flywheel’s blog. Setup vim For vim or neovim, henceforth referred to simply as “vim” (with distinctions for neovim if necessary), you will need the Vdebug plugin. Installation instructions are included on the plugin’s page. I use vim-plug to Source: https://managewp.org/articles/18538/debugging-wordpress-with-local-by-flywheel-neo-vim-and-xdebug

from Willie Chiu's Blog https://williechiu40.wordpress.com/2019/04/16/debugging-wordpress-with-local-by-flywheel-neovim-and-xdebug/

[williechiu40]

Debugging WordPress with Local by Flywheel, (neo)vim, and xdebug

Introduction Local by Flywheel is a popular tool for getting quick and reliable WordPress installations running on your computer. One of its lesser-known features is the inclusion of xdebug support. xdebug is a PHP extension that allows for real-time debugging of PHP code. Today, we’re going to go over how to get both of these working together within vim to provide a powerful interface that allows for some successful debugging of WordPress. Prerequisites Firstly, this tutorial is intended for users of vim or neovim. If you aren’t familiar with how to use vi-like editors, but want to learn, I would recommend running vimtutor in your command line and learning how to move and work in vim before continuing with this post. Next, you’ll need Local by Flywheel. You can download it here. If you haven’t set up a site before with Local, it is pretty straightforward. You can find a guide for getting started on Flywheel’s blog. Setup vim For vim or neovim, henceforth referred to simply as “vim” (with distinctions for neovim if necessary), you will need the Vdebug plugin. Installation instructions are included on the plugin’s page. I use vim-plug to from ManageWP.org https://managewp.org/articles/18538/debugging-wordpress-with-local-by-flywheel-neo-vim-and-xdebug