From: karl@freefriends.org (Karl Berry)
To: ludo@gnu.org
Cc: bug-texinfo@gnu.org, guile-devel@gnu.org
Subject: Re: makeinfo swallows page breaks
Date: Thu, 21 Mar 2013 21:56:32 GMT [thread overview]
Message-ID: <201303212156.r2LLuWq1012243@freefriends.org> (raw)
In-Reply-To: <87boacboeg.fsf@gnu.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 333 bytes --]
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 procedures
makes sense to me.
k
next prev parent reply other threads:[~2013-03-21 21:56 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
2013-03-21 21:56 ` Karl Berry [this message]
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=201303212156.r2LLuWq1012243@freefriends.org \
--to=karl@freefriends.org \
--cc=bug-texinfo@gnu.org \
--cc=guile-devel@gnu.org \
--cc=ludo@gnu.org \
/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).