As there was no (or not much?) opposition to the change, let's try to change to the mode of always running tidy before the commit.
If everyone sticks to this and if we make sure to use the same version of Perl::Tidy and the same configuration file then theoretical each tidy will only clean up the code that was changed by the developer anyway. Padre should be able to support this easily but till we have the feature you can just run perl ../tools/tidy_project.pl before the commit. In addition I added some code to the post-commit hook so after every commit the server will check if the committed files are tidy or not. It will send an e-mail to the padre-commit list if some of the files were not tidy but it won't change them. In order to make sure we use the same version of Perl::Tidy we are now checking the exact version to be '20101217' in both places. Once there is a new version of Perl::Tidy we should update the version check in both the tool/tidy_project.pl and in the post-commit hook. I hope these changes will enable us to have a smoother development path and that it will be easier to blam^h^h^ praise the committer for the changes that were made. regards Gabor _______________________________________________ Padre-dev mailing list Padre-dev@perlide.org http://mail.perlide.org/mailman/listinfo/padre-dev
