Hello I am trying to debug a PHP script and I set a breakpoint and hit to start debugging and it did what is illustrated in the screenshot and then gave this error message.
Traceback (most recent call last):
File "", line 1, in
File "/Users/gdance/.vim/bundle/vdebug/plugin/python/start_vdebug.py", line 31, in run
File "/Users/gdance/.vim/bundle/vdebug/plugin/python/vdebug/runner.py", line 137, in run
File "/Users/gdance/.vim/bundle/vdebug/plugin/python/vdebug/runner.py", line 42, in open
File "/Users/gdance/.vim/bundle/vdebug/plugin/python/vdebug/ui/vimui.py", line 28, in open
vim.command('silent tabnew ' + cur_buf_name)
Hi, it looks like there are two issues here.
The first is that where an error message should be you have some dodgy missing graphics - I don't know if that's a known issue with Macvim, but I've seen it every so often with Gvim too. The second thing looks like it's related to tabs. Do you know if your macvim has tab support built in? If not, Vdebug won't function correctly.
Try just running:
If you don't get a new tab then it's that. If not then let me know,
Interesting, it looks like the windows aren't loading up correctly. It's possible that you don't have enough vertical space to create all the necessary split windows. Are you using a fairly small display, e.g. < 15''?
Could you show me the output of this command, running it after being focussed on a full height window in your Vim:
Hope that makes sense!
Ok, thanks, it looks like the screen size is the problem. Obviously not your problem, but a problem with Vdebug :-)
Someone else raised an issue about being able to toggle windows, and I think that would solve this. However it's a pretty big overhaul, and unfortunately I'm not sure there's any short term fix that I can recommend. Having said that, it's definitely on the cards, so I'll keep you updated on any progress.
As for the key mapping, it sounds strange that changing the default mapping doesn't seem to work. I'll play around and see if I have the same problem.
The two things that you raised in the previous two messages are two separate bugs, so I've created new issues for them, #52 and #51.
No worries! Thanks for helping to improve Vdebug - you found lots of issues :)
This issue will remain open and related to the fact that small screen resolutions don't work with Vdebug yet.
Ok, thanks for the extra information.
Actually, I'm having trouble working out what the error is, because of the missing text on your Vim. Could you create a log file before running Vdebug with:
:VdebugOpt debug_file /path/to/file.log
:VdebugOpt debug_file_level 2
Then start vdebug, keep going until you get the error and then paste the output here? Or in a gist if it's too long.
Just a couple of things first off:
Right, on to the issues, working backwards.
Could you create a log file and upload it as a Gist, after having a session where the original error occurs?