Check syntax of all PHP files before an SVN commit

for i in `svn status | egrep '^(M|A)' | sed -r 's/\+\s+//' | awk '{ print $2 }'` ; do if [ ! -d $i ] ; then php -l $i ; fi ; done
Really only valuable in a PHP-only project directory. This is using standard linux versions of the tools. On most older BSD variants of sed, use -E instead of -r. Or use: sed 's/\+[[:space:]]\{1,\}//' instead.
Sample Output
No syntax errors detected in blah/crap.php
No syntax errors detected in thing/stuff.php
PHP Warning:  Unterminated comment starting line 38 in otherthing/include/bootstrap.php on line 38

2009-05-29 23:59:28

What Others Think

A frequently overlooked option of svn status is the -q "quiet" option, then you could likely avoid the egrep. For the sed|awk section if you're just looking for the filenames, then you could likely also just use cut -b 8- instead since the filenames always start at the same column.
bwoodacre · 574 weeks and 2 days 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: