l...@gnu.org (Ludovic Courtès) skribis:
> Regarding rendering: Andy noted that spaces after a sentence-ending
> periods are not preserved. I’ve investigated, but there are tests that
> assume that whitespace is collapsed, so that will require more thought.
After discussion on IRC, I committed 43
l...@gnu.org (Ludovic Courtès) skribis:
> Regarding rendering: Andy noted that spaces after a sentence-ending
> periods are not preserved. I’ve investigated, but there are tests that
> assume that whitespace is collapsed, so that will require more thought.
More precisely, Texinfo says (info "(te
l...@gnu.org (Ludovic Courtès) skribis:
> Attached is a patch to use Guile’s Texinfo support [0] to build said
> file. Guile’s Texinfo parser is incomplete but sufficient to handle
> those docstrings.
I went ahead and pushed this after discussion with Mark and Andy on IRC.
Regarding rendering:
On Thu 21 Mar 2013 22:56, k...@freefriends.org (Karl Berry) writes:
> Guile’s Texinfo parser
>
> Argh. The idea of a full second Texinfo parser in GNU is fundamentally
> wrong.
I understand where you come from. For some context on why I wrote this
parser back in 2004:
http://wingolog.org
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 p
Mike Gran skribis:
>> Attached is a patch to use Guile’s Texinfo support [0] to build said
>> file. Guile’s Texinfo parser is incomplete but sufficient to handle
>> those docstrings.
>
>> OK to commit?
>
> If Guile depends on Guile for multiple stages the build, it becomes
> difficult to recover
Hi Ludo
> Attached is a patch to use Guile’s Texinfo support [0] to build said
> file. Guile’s Texinfo parser is incomplete but sufficient to handle
> those docstrings.
> OK to commit?
If Guile depends on Guile for multiple stages the build, it becomes
difficult to recover from a problem when
l...@gnu.org (Ludovic Courtès) skribis:
> Alternately, would you suggest using a different approach?
Attached is a patch to use Guile’s Texinfo support [0] to build said
file. Guile’s Texinfo parser is incomplete but sufficient to handle
those docstrings.
It solves an actual bug for anyone usin
Hello,
Guile (ab)uses ‘makeinfo’ to generate a file, guile-procedures.txt, from
Texinfo. That file is then read at run-time to get docstrings for
Guile’s primitives.
The input looks like this (note the page breaks, aka. ^L):
--8<---cut here---start->8---
ac
