Caleb Maclennan

I'm having trouble coming up with an established example to follow... * Plenty of other macros *provide* relevant `--with-X` flags, * Others *consume the results*, * But none that I've...

Thanks @eli-schwartz. I hadn't realized a 5th argument was an option but that makes a lot of sense. Especially since no argument supplied can easily be used to maintain the...

I've worked on this for hours and hours and only turned up problems in other macros. For example the `AX_WITH_PROG` macro has a totally bogus `AS_IF` conditional where the inner...

I think I finally found an incantation that actually keeps `AC_ARG_WITH` from being expanded too soon before we know what the developer default is. I need to test some other...

Soooo, yes it's true if you call this twice with conflicting options you'll get two entries in the configure flags: ``` AX_PROG_LUA([5.1], [], [], [], [allow]) AX_PROG_LUA([5.1], [], [], [],...

I just released [sile v0.15.6](https://github.com/sile-typesetter/sile/releases/tag/v0.15.6) with exactly the macro code in 9f99895. I'll [keep an eye on distro packaging](https://github.com/sile-typesetter/sile/issues/2157) but no far so good.

Cool! One more reason to look forward to v0.10!

I just gave v0.10.0-beta.2 a spin, but it didn't work like you suggested. It did cleanup one line of code: ```diff -let demo: LuaFunction = lua.create_function(demo).unwrap(); +let demo = Function::wrap(demo);...

Oh my bad, somehow I assumed it was older and just didn't even think to look at the beta tag point! I'm working on an experimental branch mostly so I...

I gave it a shake with Git HEAD (*main* branch), and got a little further. However I struggled a but to figure out how it was going to handle errors...