Thanks for the replies.
MD> but I don't think it should be in Automake, because then the test
driver is harder to update
Fine by me :).
MD> I don't have any advise on how to get the automake maintainers
Sorry, I should have made it clear that I am, effectively, the automake
Hello Guile folk - back in May 2016, Mathieu Lirzin submitted a patch to
add a test driver for Guile Scheme to Automake.
https://lists.gnu.org/archive/html/automake-patches/2016-05/msg0.html
It was never committed. It's been seven+ years, so before doing so, I
wanted to check if it was still
Guileôòùs Texinfo parser
Argh. The idea of a full second Texinfo parser in GNU is fundamentally
wrong. If you want to call it a Guile docstring parser, whose language
happens to bear some resemblance to a subset of Texinfo, fine.
Anyway, your change to use more Guile in the Guile build
[Sorry if there has been later replies on this.]
Why is this the case? TeX itself gets this right, why can't makeinfo?
There is no overwhelming reason, it's just the historical fact that it's
never tinkered with intersentence spaces, aside from trying
half-heartedly to detect sentences at
Off-topic, but has there been any discussion of moving Guile to LGPLv3?
Not that I'm aware of, but it's a good question :). Does anyone know if
any GPLv2-only (not GPLv2-or-later) applications use Guile? That is the
main question.
Thanks,
Karl
