scan folder to check syntax error in php files

find . -name "*.php" -exec php -l {} \;

By: rbawaskar
2009-12-18 07:33:59

1 Alternatives + Submit Alt

What Others Think

This one find . -name \*.php -print0 | xargs -0 -n 1 php -l will also work if you have spaces in files and directory names
hackele · 555 weeks and 1 day ago
The command as stated already works with spaces in file/dir names because find doesn't do any tokeninzing on {} when constructing the arguments for -exec, since it isn't passing the command off to a shell, it's executing it directly. But if you said "-exec php -l {} a b c" then the shell would tokenize a,b,c into different arguments before find even starts, so to treat "a b c" as a single argument you just need to quote it. So xargs isn't necessary here.
bwoodacre · 555 weeks and 1 day ago
hm. true.
hackele · 555 weeks and 1 day ago

What do you think?

Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?

You must be signed in to comment.

What's this? is the place to record those command-line gems that you return to again and again. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.

Share Your Commands

Stay in the loop…

Follow the Tweets.

Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.


Subscribe to the feeds.

Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):

Subscribe to the feed for: