unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Gavin Smith <GavinSmith0123@gmail.com>
Cc: guix-devel@gnu.org, Andy Wingo <wingo@igalia.com>,
	Texinfo <bug-texinfo@gnu.org>
Subject: Re: Any interest in using HTML for locally-installed Texinfo documentation?
Date: Thu, 04 Apr 2019 18:02:38 +0200	[thread overview]
Message-ID: <87o95lrc69.fsf@gnu.org> (raw)
In-Reply-To: <20190404102320.GA6369@darkstar.lan> (Gavin Smith's message of "Thu, 4 Apr 2019 11:23:20 +0100")

Hi Gavin,

Gavin Smith <gavinsmith0123@gmail.com> skribis:

> On Wed, Apr 03, 2019 at 11:11:36PM +0200, Ludovic Courtès wrote:

[...]

>> I was mentioning this because it’s an experiment that Andy Wingo did
>> about 15 years (?!) ago.  Andy wrote the Texinfo parser that’s now part
>> of Guile, and then had a Guile-GTK program that used a tree widget to
>> show the contents, had clickable links, text would reflow, etc.  (See
>> <https://wingolog.org/archives/2004/07/25/literate-programming-with-guile-lib>.
>> Unfortunately the screenshot has disappeared.)
>> 
>> That said, it surely is quite a bit of work, but I think it’s an option
>> we could consider.
>
> This is an interesting idea.  How far developed was the program?  Is it 
> still extant?

This was a pure Guile approach.  The parser itself has been part of
Guile since 2.0; it’s good but incomplete (usually it cannot parse
complete manuals.)

The viewer was based on Guile-GNOME, which was in the GTK+2 era I
believe.  It definitely wouldn’t be usable as-is today.  Andy, do you
remember more?  :-)

Thanks,
Ludo’.

  reply	other threads:[~2019-04-04 16:02 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-01 12:55 Any interest in using HTML for locally-installed Texinfo documentation? Gavin Smith
2019-04-01 14:01 ` sirgazil
2019-04-02  9:37 ` Ludovic Courtès
2019-04-02 15:02   ` Gavin Smith
2019-04-02 16:46     ` Per Bothner
2019-04-07 16:28       ` Gavin Smith
2019-04-08 15:12         ` Ludovic Courtès
2019-04-08 15:39           ` Pierre Neidhardt
2019-04-08 23:46           ` Gavin Smith
2019-04-09  6:25             ` Eli Zaretskii
2019-04-13 16:21           ` Gavin Smith
2019-04-14 19:25             ` Pronaip
2019-10-15 19:27             ` Gavin Smith
2019-10-15 20:20               ` P
2019-10-15 20:35                 ` Gavin Smith
2019-10-15 20:40                 ` Per Bothner
2019-10-15 21:00                   ` Gavin Smith
2019-10-15 21:09                     ` Per Bothner
2019-10-15 21:30                       ` Gavin Smith
2019-10-16  1:39               ` Ricardo Wurmus
2019-10-19 20:31               ` Ludovic Courtès
2019-10-22 19:00                 ` Gavin Smith
2019-10-22 20:18                   ` Gavin Smith
2019-11-03 14:04                   ` Ludovic Courtès
2019-11-03 15:37                     ` Gavin Smith
2019-11-06 21:49                       ` Ludovic Courtès
2019-04-03 21:21     ` Ludovic Courtès
2019-04-04 10:33       ` Gavin Smith
2019-04-02 15:31   ` Per Bothner
2019-04-03 21:11     ` Ludovic Courtès
2019-04-03 22:44       ` Per Bothner
2019-04-04 10:23       ` Gavin Smith
2019-04-04 16:02         ` Ludovic Courtès [this message]
2019-04-02 20:12   ` Ricardo Wurmus
2019-04-02 20:27     ` Ricardo Wurmus
2019-04-02 22:58       ` sirgazil
2019-04-02 22:10     ` Per Bothner
2019-04-02 23:09       ` sirgazil
2019-04-03  8:43         ` Gavin Smith
2019-04-03 14:23           ` sirgazil
2019-04-03 14:40             ` Per Bothner
2019-04-03 14:49       ` Ricardo Wurmus
2019-04-02 21:02 ` George Clemmer
2019-04-07 11:08   ` Gavin Smith

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://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87o95lrc69.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=GavinSmith0123@gmail.com \
    --cc=bug-texinfo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=wingo@igalia.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. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).