unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: karl@freefriends.org (Karl Berry)
Cc: ludo@gnu.org, bug-texinfo@gnu.org, guile-devel@gnu.org
Subject: Re: makeinfo swallows page breaks
Date: Fri, 22 Mar 2013 11:14:10 +0100	[thread overview]
Message-ID: <87mwtvu4gd.fsf@pobox.com> (raw)
In-Reply-To: <201303212156.r2LLuWq1012243@freefriends.org> (Karl Berry's message of "Thu, 21 Mar 2013 21:56:32 GMT")

On Thu 21 Mar 2013 22:56, karl@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/archives/2006/11/17/high-on-sodium-vapor

I even had a gtk browser at one point with help:

  http://wingolog.org/pub/texinfo-browser.png

I had a GTK app then with context-sensitive interactive help.  So I
needed to treat docs programmatically.

> If you want to call it a "Guile docstring parser, whose language
> happens to bear some resemblance to a subset of Texinfo", fine.

It is intended to be a strict subset.  To do otherwise we would have to
make a new format, and that would be bad.

Cheers,

Andy
-- 
http://wingolog.org/



  reply	other threads:[~2013-03-22 10:14 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
2013-03-22 10:14     ` Andy Wingo [this message]
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=87mwtvu4gd.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=bug-texinfo@gnu.org \
    --cc=guile-devel@gnu.org \
    --cc=karl@freefriends.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).