On 08/09/16 13:26, Niklas Keller wrote: > That is the chicken ... if you ARE already composer user then it will > make some sense, but pear gives a phpcs -h which works out of the box. > ./vendor/bin/phpcs -h does not sound right as an alternative? > > Why does it seem not right? It's perfectly right and the way to go if > you're using Composer. > > An alternative would be to use Composer's global require and adding the > global "bin" directory of Composer to your PATH variable.
bash: ./vendor/bin/phpcs: No such file or directory Which I presume means I do need to set up some path, but currently I no idea where 'composer global require "squizlabs/php_codesniffer=*"' has put it? > And I > would expect different installations of composer will affect that > installation? > > What do you mean by "affect that installation"? Currently having followed the installation guide I have things working on a home directory. This is probably what people expect today, but I still expect tools to be available which ever login I use ... testing different client profiles. -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
