max_data is limited to 1024 about vdebug HOT 4 CLOSED

On Sun, 3 Mar 2013, Jimmy-M-G wrote:

Thanks for your great job. I like your plugin very much. It seems you
limit the string length to '1024', and the string length can be only
displayed with a limit length, though I set
'xdebug.var_display_max_data=-1' on xdebug.ini to enable the string
length to unlimit.

This var_display_max_data setting is not meant to be used for the
debugging protocol. That has a specific command to set the max data
size.

cheers,
Derick

Like Xdebug? Consider a donation: http://xdebug.org/donate.php
Xdebug | http://xdebug.org | [email protected]
twitter: @derickr and @xdebug

from vdebug.

I can enlarge the max_data for a string variable, with python command, "api.feature_set('max_depth', 2048)" to invoke "feature_set -i transaction_id -n feature-name -v value".
But, how to do it using gvim. Could you give me more details? Should I set the value in some option or not? I wanna view the full string value when I press "F11". But, now it is only display a limit string length on the VdebugWatchWindow.
cheers,
Jimmy.

from vdebug.

The great thing about getting an answer from @derickr about Xdebug is that it's almost certainly right :-D

I'll add a Vdebug option to allow you to set the value of the max_depth feature, and it will arrive in the next version.

Thanks

from vdebug.

This is now available in the dev branch, and soon to be in the upcoming version 1.4.0.

Use the g:vdebug_features dictionary to set name/value pairs of features to be sent to the debugger (according to the DBGP spec). E.g:

let g:vdebug_features['max_depth'] = 2048

Every time you start a new debugging session this will be re-read, and all features are set at the beginning of the connection.

Thanks

from vdebug.