Hal Murray via devel writes:
> It seemed like a simplle/clean edit. I wonder what I missed.
My admonition some time ago that this is more complicated than you
seemed to think? In a strange way I'm relieved it blows up so quickly,
though.
You would really need to set up a testing rig that can sh
>Hal Murray hmurray at megapathdsl.net wrote:
>Fri Dec 6 11:47:41 UTC 2019
>
>I just pushed it.
>
>Default is no change. If you add --disable-fuzz to your configure line,
>almost all that code goes away.
>
>The "almost" is because ifdef-s don't work in bison input. So "tinker tick
>" still gets
