On Thu, Aug 11, 2011 at 10:05 AM, Sebastian Willing <sebastian.will...@web.de> wrote: > Hi, > > The blank line issue commit had a syntax failure in another file, Padre > didn't even start using r15294, but it's eol related and might not > happen on windows. This is ok, but we have so many linux users here and > they didn't complain, too.
I have been using almost exclusively Windows in the last 2 weeks so if this was a bug that manifested only on Linux then that might explain why I did not see it. OTOH I am sometimes tired of some of these obvious bugs that enter the Padre code base and only report it on the IRC channel and sometimes - especially when I am on Windows where my IRC access is not that obvious, not even there. This is not good but I think this is the side effect of accumulated tiredness of these issues. > > Find in files (Ctrl+F three times) was broken by missing $ signs (r15328 > lines 1201 and following): > > my $findinfiles = Padre::Wx::Dialog::FindInFiles->new($main); > findinfiles->find_term->SetValue($term); > findinfiles->run; > findinfiles->Destroy; > These things can happen but especially as we don't have enough automated tests I would expect that all of us are going to try manually the parts of the code that are effected by our changes at least on our regular operating system. I know it slows down our work and it might not be so much fun for volunteer developers but it is a courtesy to our other fellow volunteers (read everyone else) so they won't have to fix others regression bugs too often. Always running trunk and keep restarting Padre helps in locating these issues. regards Gabor _______________________________________________ Padre-dev mailing list Padre-dev@perlide.org http://mail.perlide.org/mailman/listinfo/padre-dev
