Yes. Thanks! I thought of the workaround right after I localized the
cause down to the example. It is just that the idea of legitimate
command sequence causing segfault makes me uncomfortable - so I emailed.
I mean, this should ideally be either documented (lol) or some other
workaround implemented so that no segfaults happen with non-user written
code.
Well, in any case, the workaround does its job.
--
Sergey
Bernd Paysan wrote:
Hm, seens to be that oof.fb installs some hooks which aren't removed by
the marker.
If you want to get around this, I suggest to write
\needs object include oof.fb
marker testing
...
testing
marker testing
...
testing
This makes sure that oof.fb is loaded only once, and you can reload the
surrounding file as often as you like.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]