From: "Thompson, David" <dthompson2@worcester.edu>
To: Chad Albers <calbers@neomantic.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>, guile-devel <guile-devel@gnu.org>
Subject: Re: Contributions to Guile
Date: Mon, 8 Feb 2016 16:37:23 -0500 [thread overview]
Message-ID: <CAJ=RwfaeF4U1T4+FcviXYue7L_d=B-MyLbz33KFz5nbcv4hjkg@mail.gmail.com> (raw)
In-Reply-To: <CA+tCiVYZ-O4RGsM4cd4oOuc6n3mX4i0838Bi=GWduUbMgaHahA@mail.gmail.com>
On Mon, Feb 8, 2016 at 4:28 PM, Chad Albers <calbers@neomantic.com> wrote:
> On Mon, Feb 8, 2016 at 2:05 PM, Christopher Allan Webber
> <cwebber@dustycloud.org> wrote:
>> Ludovic Courtès writes:
>>
>>> Christopher Allan Webber <cwebber@dustycloud.org> skribis:
>>>
>>>> Chad Albers writes:
>>>
>>> [...]
>>>
>>>>> b. More robust documentation system - texinfo is not the greatest. And
>>>>> it's non-trivial to generate any documentation (including texinfo) for
>>>>> modules.
>>>>
>>>> Texinfo is pretty nice to use if you're an emacs user... in fact, if
>>>> you're an emacs user, it's the best documentation reading system in the
>>>> world. But not everyone's an emacs user.
>>>
>>> I think Texinfo is OK even if you’re not an Emacs user, no? Especially
>>> with the just-release 6.1 where menus can (finally!) be automatically
>>> generated.
>>>
>>>> If the html export was nicely themed
>
> IMHO, HTML has clearly won the documentation game. I believe it goes
> without saying that most developers have a web browser installed,
> rather than a textinfo reader. The more the guile project publishes
> easily searchable (without google) documentation in the most
> accessible media format the better for guile.
We can clearly have both. Nice looking HTML docs on the Guile website
are possible with a little CSS magic and some nice fonts. Thanks to
Texinfo, we also get Info and PDF versions! Having the Guile
documentation nicely integrated with my editor (Emacs) is a *huge*
productivity booster. Having HTML-only documentation would be a major
setback for Guile.
- Dave
next prev parent reply other threads:[~2016-02-08 21:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-17 18:43 Contributions to Guile Chad Albers
2016-02-05 9:32 ` Ludovic Courtès
2016-02-05 9:56 ` Sergi
2016-02-07 19:25 ` Chad Albers
2016-02-07 22:23 ` Christopher Allan Webber
2016-02-08 2:25 ` Mike Gerwitz
2016-02-08 11:31 ` Alex Sassmannshausen
2016-02-08 17:55 ` Christopher Allan Webber
2016-02-08 8:06 ` Ludovic Courtès
2016-02-08 18:17 ` Christopher Allan Webber
2016-02-08 19:22 ` Ricardo Wurmus
2016-02-08 20:28 ` Ludovic Courtès
2016-02-08 22:06 ` Ricardo Wurmus
2016-02-08 22:58 ` Ludovic Courtès
2016-02-08 19:05 ` Christopher Allan Webber
2016-02-08 20:31 ` Ludovic Courtès
2016-02-08 21:28 ` Chad Albers
2016-02-08 21:37 ` Thompson, David [this message]
2016-02-09 16:09 ` Chad Albers
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='CAJ=RwfaeF4U1T4+FcviXYue7L_d=B-MyLbz33KFz5nbcv4hjkg@mail.gmail.com' \
--to=dthompson2@worcester.edu \
--cc=calbers@neomantic.com \
--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).