bgribble/mfp

Cycles triggered by onload/loadbang prevent patch loading

Closed this issue · 1 comments

A buggy patch that would never have worked should nonetheless be loadable and editable. Right now, if an onload or loadbang behavior causes an infinite loop the patch will never complete loading. Maybe this should be part of a refactoring to move all "work" processing into a single queue?

I'm going to close this for now. The --no-onload option basically does what's needed. Detecting and breaking cycles is a bit out of scope.