Comments (7)
Completely understood! Sorry for the misunderstanding. Don't worry about bringing a support question - where else are you going to be able to get support for Vdebug anyway? :-P
You've raised a point actually - I think I need to add something to check whether the g:vdebug_features
dictionary has already been initialized, so you can use:
let g:vdebug_features = { 'max_children': 128 }
At the moment that won't work if Vdebug gets loaded afterwards, as the dictionary will get overwritten. I'll make that the focus of this issue.
Cheers
from vdebug.
Yeah, I ran into this as well -- takes a long time to figure out your debugger's broken
from vdebug.
@michaelfavia thanks for the detailed information.
Yeah, I ran into this as well -- takes a long time to figure out your debugger's broken
@aaronhuckabee that's completely unhelpful. @aaronhuckabee sorry for the misunderstanding :)
Take a look at #55, as it's relevant. @derickr, the author of Xdebug, pointed out that the xdebug INI settings don't relate to the settings for the debugging connection - for that you want features. One of the features you can set is how many children you display, max_children, and you can see all the other features here.
If you upgrade to the latest version of Vdebug (1.4.0) then you can set these features easily in the g:vdebug_features
dictionary in your .vimrc:
" Somewhere in your .vimrc after loading vdebug
let g:vdebug_features['max_children'] = 128
Hope that makes sense. Thanks
from vdebug.
@joonty: I actually know @aaronhuckabee and forwarded him the issue when i made it so he could follow along as he was similarly affected.
He didn't mean your (joonty) debugger is broken he meant your (his) debugger is broken because he was looking through an associative array and the keys were missing but there was no indication that it was a truncated list of the array so he didnt know it was a configuration error and assumed it was his code. He literally sat there trying to figure out where his array elements were until we finally resorted to print_r() ing them to check to see if his debugger was lying to him. ;)
I think he was just trying to confirm the issue for us. He one of the good guys. ;)
That aside: I was able to load this setting in vim and the debugger worked perfectly (WFM). Thank you for your help and sorry to bring an apparent support request to your queue.
For some reason my Spf13 instance is loading the local modification sources in the wrong order so i cant add it to my .vimrc.local or .vimrc.bundles.fork because the variables havent been defined yet and it causes errors on vim startup but thats an upstream issue i think. spf13/spf13-vim#314
Thanks again.
from vdebug.
Forgot to reference this issue in the commit name. This is fixed in commit 699ab0e
from vdebug.
(largely useless comment)
My apologies -- I didn't consider how it sounded before posting, and was only trying to add weight to the issue by confirmation.
Many thanks for the module -- I find it extremely useful.
from vdebug.
This particular example of array truncating is worth adding to FAQ - it may save time someone.
I just spent 20 minutes trying to find $_SERVER['REQUEST_URI']
.
My english is too poor to add my own patch ;).
from vdebug.
Related Issues (20)
- modern vdebug: does it play nicely with neovim and xdebug v3.0.2?
- nvim freezes on xdebug connection, then `Error starting Vdebug: <class 'EOFError'>` in the statusline
- Option to disable automatic updating of watch window
- No module found 'dbgp' but I am in a dbgp directory HOT 1
- VdebugEval! Can't get values of array at depth > 1 HOT 3
- Wrong reference in the VimPlug instalation at VimAwesome
- Python program stuck after debugging finish (cursor reach end of program)
- Infinite-ish recursion on singleton classes HOT 1
- No option with key 'autostart' HOT 1
- Vim hangs up connection without stopping on breaking point HOT 3
- Cannot expand or collapse HOT 1
- TypeError when empty xml elements in response HOT 1
- Are there plans for a new release?
- Update README PHP setup with Xdebug HOT 1
- Security concern
- Problems defining close keymap in neovim with lazy plugin manager
- Path maps not working HOT 1
- Error detected while processing /Users/***/vdebug.vim[343]..function Vdebug_load_options[8]..<SNR>11_DefineSigns HOT 1
- Setting up Vdebug without php.ini access
- Syntax warning: invalid escape sequence HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from vdebug.