From 8a4a27e4509dd32a8a209f8a3cd78ee36db24a03 Mon Sep 17 00:00:00 2001 From: Patrik Lermon Date: Thu, 25 Feb 2016 10:27:47 +0100 Subject: [PATCH] Update troubleshooting.md --- doc/articles/troubleshooting.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/doc/articles/troubleshooting.md b/doc/articles/troubleshooting.md index f7802115c..fd805b3f4 100644 --- a/doc/articles/troubleshooting.md +++ b/doc/articles/troubleshooting.md @@ -202,7 +202,9 @@ echo 'function composer() { COMPOSER="$(which composer)" && sudo php5dismod -s c . ~/.bash_aliases ``` -When executing `composer` you will run it with xdebug **disabled** (**as long as the command is executing**), andy if you execute composer using explicit path (like `./composer` or `/usr/local/bin/composer`) xdebug will be **enabled**. +When executing `composer` you will run it with xdebug **disabled** (**as long as the command is executing**), +and if you execute composer using explicit path (like `./composer` or `/usr/local/bin/composer`) +xdebug will be **enabled**. If you do not want to disable it and want to get rid of the warning you can also define the [COMPOSER_DISABLE_XDEBUG_WARN](../03-cli.md#composer-disable-xdebug-warn) environment variable.