packages: php-pecl-xdebug/php-pecl-xdebug.ini - fix bad chars
glen
glen at pld-linux.org
Tue Jul 7 19:34:39 CEST 2009
Author: glen Date: Tue Jul 7 17:34:39 2009 GMT
Module: packages Tag: HEAD
---- Log message:
- fix bad chars
---- Files affected:
packages/php-pecl-xdebug:
php-pecl-xdebug.ini (1.1 -> 1.2)
---- Diffs:
================================================================
Index: packages/php-pecl-xdebug/php-pecl-xdebug.ini
diff -u packages/php-pecl-xdebug/php-pecl-xdebug.ini:1.1 packages/php-pecl-xdebug/php-pecl-xdebug.ini:1.2
--- packages/php-pecl-xdebug/php-pecl-xdebug.ini:1.1 Mon Nov 26 23:21:38 2007
+++ packages/php-pecl-xdebug/php-pecl-xdebug.ini Tue Jul 7 19:34:33 2009
@@ -50,7 +50,7 @@
; This setting tells Xdebug to gather information about which variables are
; used in a certain scope. This analysis can be quite slow as Xdebug has to
-; reverse engineer PHP?s opcode arrays. This setting will not record which
+; reverse engineer PHP's opcode arrays. This setting will not record which
; values the different variables have, for that use xdebug.collect_params.
; This setting needs to be enabled only if you wish to use
; xdebug_get_declared_vars().
@@ -59,7 +59,7 @@
; If this setting is On then stacktraces will be shown by default on an error
; event. You can disable showing stacktraces from your code with xdebug_disable().
; As this is one of the basic functions of Xdebug, it is advisable to leave this
-; setting set to ?On?.
+; setting set to 'On'.
xdebug.default_enable=On
; These seven settings control which data from the superglobals is shown when an
@@ -87,9 +87,9 @@
; setting to On, otherwise leave it set to Off.
xdebug.dump_undefined=Off
-; Controls whether Xdebug should enforce ?extended_info? mode for the PHP parser;
+; Controls whether Xdebug should enforce 'extended_info' mode for the PHP parser;
; this allows Xdebug to do file/line breakpoints with the remote debugger. When
-; tracing or profiling scripts you generally want to turn off this option as PHP?s
+; tracing or profiling scripts you generally want to turn off this option as PHP's
; generated oparrays will increase with about a third of the size slowing down
; your scripts. This setting can not be set in your scripts with ini_set(), but
; only in php.ini.
@@ -110,7 +110,7 @@
; The default is based on environment settings. First the environment setting
; DBGP_IDEKEY is consulted, then USER and as last USERNAME. The default is set
; to the first environment variable that is found. If none could be found the
-; setting has as default ?.
+; setting has as default.
xdebug.idekey=
; This is the base url for the links from the function traces and error message
@@ -126,7 +126,7 @@
; Introduced in Xdebug 2.1
; By default Xdebug overloads var_dump() with its own improved version for displaying
; variables when the html_errors php.ini setting is set to 1. In case you do not
-; want that, you can set this setting to 0, but check first if it?s not smarter
+; want that, you can set this setting to 0, but check first if it's not smarter
; to turn off html_errors.
xdebug.overload_var_dump=On
@@ -135,7 +135,7 @@
; Instead the file will be appended to with the new profile.
xdebug.profiler_append=0
-; Enables Xdebug?s profiler which creates files in the profile output directory.
+; Enables Xdebug's profiler which creates files in the profile output directory.
; Those files can be read by KCacheGrind to visualize your data. This setting
; can not be set in your script with ini_set().
xdebug.profiler_enable=0
@@ -158,7 +158,7 @@
xdebug.profiler_output_name=cachegrind.out.%p
; Normally you need to use a specific HTTP GET/POST variable to start remote debugging.
-; When this setting is set to ?On? Xdebug will always attempt to start a remote
+; When this setting is set to 'On' Xdebug will always attempt to start a remote
; debugging session and try to connect to a client, even if the GET/POST/COOKIE
; variable was not present.
xdebug.remote_autostart=Off
@@ -169,8 +169,8 @@
; just continue as if this setting was Off.
xdebug.remote_enable=Off
-; Can be either ?php3? which selects the old PHP 3 style debugger output, ?gdb?
-; which enables the GDB like debugger interface or ?dbgp? - the brand new debugger
+; Can be either 'php3' which selects the old PHP 3 style debugger output, 'gdb'
+; which enables the GDB like debugger interface or 'dbgp' - the brand new debugger
; protocol. The DBGp protocol is more widely supported by clients. See more
; information in the introduction for Remote Debugging.
xdebug.remote_handler=dbgp
@@ -199,12 +199,12 @@
; exception is raised - even if this exception is actually caught.
xdebug.show_exception_trace=0
-; When this setting is set to something != 0 Xdebug?s generated stack dumps in
+; When this setting is set to something != 0 Xdebug's generated stack dumps in
; error situations will also show all variables in the top-most scope. Beware
; that this might generate a lot of information, and is therefore turned off by default.
xdebug.show_local_vars=0
-; When this setting is set to something != 0 Xdebug?s human-readable generated
+; When this setting is set to something != 0 Xdebug's human-readable generated
; trace files will show the difference in memory usage between function calls.
; If Xdebug is configured to generate computer-readable trace files then they
; will always show this information.
@@ -219,7 +219,7 @@
; are different records for entering a stack frame, and leaving a stack frame
xdebug.trace_format=0
-; When set to ?1? the trace files will be appended to, instead of being overwritten
+; When set to '1' the trace files will be appended to, instead of being overwritten
; in subsequent requests.
xdebug.trace_options=0
@@ -230,7 +230,7 @@
; This setting determines the name of the file that is used to dump traces into.
; The setting specifies the format with format specifiers, very similar to
; sprintf() and strftime(). There are several format specifiers that can be used
-; to format the file name. The ?.xt? extension is always added automatically.
+; to format the file name. The '.xt' extension is always added automatically.
;The possible format specifiers are:
; %c crc32 of the current working directory trace.%c trace.1258863198.xt
; %p pid trace.%p trace.5174.xt
@@ -238,13 +238,13 @@
; %s script name cachegrind.out.%s cachegrind.out._home_httpd_html_test_xdebug_test_php
; %t timestamp (seconds) trace.%t trace.1179434742.xt
; %u timestamp (microseconds) trace.%u trace.1179434749_642382.xt
-; %H $_SERVER[?HTTP_HOST?] trace.%H trace.kossu.xt
-; %R $_SERVER[?REQUEST_URI?] trace.%R trace._test_xdebug_test_php_var=1_var2=2.xt
+; %H $_SERVER['HTTP_HOST'] trace.%H trace.kossu.xt
+; %R $_SERVER['REQUEST_URI'] trace.%R trace._test_xdebug_test_php_var=1_var2=2.xt
; %S session_id (from $_COOKIE if set) trace.%S trace.c70c1ec2375af58f74b390bbdd2a679d.xt
; %% literal % trace.%% trace.%%.xt
xdebug.trace_output_name=trace.%c
-; Controls the amount of array children and object?s properties are shown when
+; Controls the amount of array children and object's properties are shown when
; variables are displayed with either xdebug_var_dump(), xdebug.show_local_vars
; or through Function Traces. This setting does not have any influence on the
; number of children that is send to the client through the Remote Debugging feature.
================================================================
---- CVS-web:
http://cvs.pld-linux.org/cgi-bin/cvsweb.cgi/packages/php-pecl-xdebug/php-pecl-xdebug.ini?r1=1.1&r2=1.2&f=u
More information about the pld-cvs-commit
mailing list