From: ludo@gnu.org (Ludovic Courtès)
To: Mike Gran <spk121@yahoo.com>
Cc: "guile-devel@gnu.org" <guile-devel@gnu.org>
Subject: Re: makeinfo swallows page breaks
Date: Thu, 21 Mar 2013 21:31:08 +0100 [thread overview]
Message-ID: <87r4j8a41f.fsf@gnu.org> (raw)
In-Reply-To: <1363892280.87140.YahooMailNeo@web120406.mail.ne1.yahoo.com> (Mike Gran's message of "Thu, 21 Mar 2013 11:58:00 -0700 (PDT)")
Mike Gran <spk121@yahoo.com> 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 from a problem when the build is failing.
Well, that’s nothing compared to its bootstrapping procedure. :-)
> So maybe this commit will lead to better, more methodical hacking; maybe
> it will make fixing a broken Guile more annoying.
It will force us to maintain the Texinfo modules at a reasonable level,
which I think it’s good. Hopefully, if something breaks, it will break
deterministically.
Conversely, here people with Texinfo 5.x get no docstrings (and thus
failing tests), people with an older Texinfo don’t have any problems,
and people without Texinfo have no problem but their docstrings include
unprocessed markup.
Overall, I really think it’s an improvement.
Ludo’.
next prev parent reply other threads:[~2013-03-21 20:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 23:14 makeinfo swallows page breaks Ludovic Courtès
2013-03-21 18:25 ` Ludovic Courtès
2013-03-21 18:58 ` Mike Gran
2013-03-21 20:31 ` Ludovic Courtès [this message]
2013-03-21 21:56 ` Karl Berry
2013-03-22 10:14 ` Andy Wingo
2013-03-22 10:33 ` Ludovic Courtès
2013-03-22 10:56 ` Ludovic Courtès
2013-03-22 21:42 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r4j8a41f.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
--cc=spk121@yahoo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).