OK, I'll write a patch when I get home :) However, what should the filtering behavior be? I think the best solution would be to ignore everything that can't contain a valid perl package (C<package .#foo> is a compile error, as is C<package foo~>) That way vi (or kate / gedit / whatever) users get the bugfix too :)
Also (in response to apv), changing the restart regex won't fix things. If your emacs crashed (or rather, you killed the X session without closing emacs first, in my case), your catalyst server won't be able to start until you cleanup the tempfiles with M-x recover-session or careful use of C<rm>. :) Regards, Jonathan Rockway Kieren Diment wrote: > Right, > > Catalyst used to use Module::Plugable::Fast for component autodiscovery > > Now it uses Module::Pluggable::Object. > > This behaviour was fixed for M::P::F a while back but evidently hasn't > been for M::P::O (and MPO produces a more cryptic error message too :( > ). So if you're up to it, rtfs for both, make a patch for MPO and > send it to the author or to RT noting that the behaviour was fixed in > MPF a while back. > > > On 28/07/06, *apv* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote: > > I complained about this quite some time ago and was told to use the > "restartregex" option to filter that out (and "scratch_file~" of > course). Instead of suggesting that, I'll join in in complaining > again. :) > _______________________________________________ List: [email protected] Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[email protected]/ Dev site: http://dev.catalyst.perl.org/
