You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
My issue is related to the configuration of the Installed PHPs interpreters.
In 'Windows | Preferences | PHP | Installed PHPs' you can configure the available
PHP interpreters by pressing the Add button. The window that appears allows you to set
the interpreter and the configuration files read by it.
Issue 1
The label of the checkbox "Use system default php.ini configuration" should
be changed to something more suggestive. The actual label makes explicit
reference to the name php.ini. Nothing in this label sugggests that this
checkbox is related to the "Additional .ini files parsed" by the
interpreter. The php interpreter itself prints "Additional .ini files
parsed:" when run with the --ini option and this checkbox controls exactly this
set of files.
Issue 2
The options in this window allow us to configure the execution environment of the PHP
interpreter by specifying the php.ini file and providing some degree (but not complete) of
control over the "Additional .ini file parsed".
These execution environments will be referenced when creating Run Configurations.
Let's assume the following:
I have configured a PHP interpreter that loads only the file php.ini.
I have a script main.php that I want to debug.
Because the debugger is not loaded, I have to create a new Run Configuration and specify
through PHP_INI_SCAN_DIR to scan a directory that contains the file xdebug.ini that in turn
loads xdebug.so.
This is the only way of doing that. It is not possible to use the checkbox "Use
system default php.ini configuration" because the interpreter could load more
files that I want.
Now, if I create another file, let's call it webpage.php, and I want to debug it
I have to create a run configuration for it and specify again to load xdebug.ini.
It would be more convenient if we could add a PHP interpreter and specify all
additional ini files that must be loaded.
In this way I could create two configurations:
PHP - no debug that loads only the file php.ini;
PHP - with debug that loads both php.ini and xdebug.ini;
Then the Run Configurations of main.php and webpage.php would reference
these configurations without the need of specifying PHP_INI_SCAN_DIR each time
in the run configuration of a script that I want to to debug.
Is this feature require new UI elements or modify existing?
In 'Windows | Preferences | PHP | Installed PHPs / Add... "
* Change the label of the checkbox "Use system default php.ini configuration"
* Allow to set the contents of PHP_INI_SCAN_DIR.
Describe the solution you'd like
... see above
Describe alternatives you've considered
No to attain what I want, that is to launch a PHP interpeter that loads xdebug.ini I've created the following script:
---- begin php8.2-dbg-only.sh ----
PHP_INI_SCAN_DIR=/home/bob//php/tools/additional-ini-debug /usr/bin/php8.2 "$@"
---- php8.2-dbg-only.sh ----
And I configure this script in Installed PHPs.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
My issue is related to the configuration of the Installed PHPs interpreters.
In 'Windows | Preferences | PHP | Installed PHPs' you can configure the available
PHP interpreters by pressing the Add button. The window that appears allows you to set
the interpreter and the configuration files read by it.
Issue 1
The label of the checkbox "Use system default php.ini configuration" should
be changed to something more suggestive. The actual label makes explicit
reference to the name php.ini. Nothing in this label sugggests that this
checkbox is related to the "Additional .ini files parsed" by the
interpreter. The php interpreter itself prints "Additional .ini files
parsed:" when run with the --ini option and this checkbox controls exactly this
set of files.
Issue 2
The options in this window allow us to configure the execution environment of the PHP
interpreter by specifying the php.ini file and providing some degree (but not complete) of
control over the "Additional .ini file parsed".
These execution environments will be referenced when creating Run Configurations.
Let's assume the following:
Because the debugger is not loaded, I have to create a new Run Configuration and specify
through PHP_INI_SCAN_DIR to scan a directory that contains the file xdebug.ini that in turn
loads xdebug.so.
This is the only way of doing that. It is not possible to use the checkbox "Use
system default php.ini configuration" because the interpreter could load more
files that I want.
Now, if I create another file, let's call it webpage.php, and I want to debug it
I have to create a run configuration for it and specify again to load xdebug.ini.
It would be more convenient if we could add a PHP interpreter and specify all
additional ini files that must be loaded.
In this way I could create two configurations:
Then the Run Configurations of main.php and webpage.php would reference
these configurations without the need of specifying PHP_INI_SCAN_DIR each time
in the run configuration of a script that I want to to debug.
Is this feature require new UI elements or modify existing?
In 'Windows | Preferences | PHP | Installed PHPs / Add... "
* Change the label of the checkbox "Use system default php.ini configuration"
* Allow to set the contents of PHP_INI_SCAN_DIR.
Describe the solution you'd like
... see above
Describe alternatives you've considered
No to attain what I want, that is to launch a PHP interpeter that loads xdebug.ini I've created the following script:
---- begin php8.2-dbg-only.sh ----
PHP_INI_SCAN_DIR=/home/bob//php/tools/additional-ini-debug /usr/bin/php8.2 "$@"
---- php8.2-dbg-only.sh ----
And I configure this script in Installed PHPs.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: