So if I understand you, then you would even get rid of the tools/tidy_project.pl and expect that everyone will use Padre to edit the source code of Padre and also use the Perl::Tidy plugin which would run tidy before saving the file.
I think that would be acceptable though it would require some more development on our part as currently the tidy plugin cannot register to be called upon save. Till we implement that and probably even after that we will need some discipline from ourselves. To make it sure we educate ourselves I could add a post-commit hook that will check if the most recently committed files are clean and send a warning e-mail if there is anything to tidy. We can then require the payment of one bottle of beer[1] by the person who committed an untidy file. Gabor [1] or equivalent amount of chocolate. On Mon, Feb 28, 2011 at 2:39 PM, Adam Kennedy <adamkennedybac...@gmail.com> wrote: > Occasionally I switch temporarily when I completely destroy something > internal, but I will be back in Padre before I do the final commit. > > Adam K > > > On 28 February 2011 23:20, Claudio Ramirez <padre.clau...@apt-get.be> wrote: >> Op 28-02-11 13:19, Adam Kennedy schreef: >>> Padre is an IDE, and one that supports Perl Tidy, AND one that >>> theoretically supports project-specific configuration. >>> >>> I think it's a bad idea to do tidying anywhere other than client side, >>> and I think the IDE itself should enforce the tidying. >> >> It does not happen to you that you use vim or an other editor when >> fixing a crashing Padre? _______________________________________________ Padre-dev mailing list Padre-dev@perlide.org http://mail.perlide.org/mailman/listinfo/padre-dev
