From: ludo@gnu.org (Ludovic Courtès)
To: Christopher Allan Webber <cwebber@dustycloud.org>
Cc: guile-devel@gnu.org
Subject: Re: Contributions to Guile
Date: Mon, 08 Feb 2016 21:31:43 +0100 [thread overview]
Message-ID: <87io1zueog.fsf@gnu.org> (raw)
In-Reply-To: <87twljxbuq.fsf@dustycloud.org> (Christopher Allan Webber's message of "Mon, 08 Feb 2016 11:05:21 -0800")
Christopher Allan Webber <cwebber@dustycloud.org> skribis:
> 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
>>
>> It can be nicely themed. FWIW, Gnulib’s gendocs.sh, which is what most
>> projects use to export their HTML to gnu.org, now includes a CSS by
>> default (see <https://gnu.org/s/guix/manual> as an example.) We can
>> change this CSS anytime, and in fact, I would love it if someone
>> talented would come up with improvements!
>
> Relatedly, see this very conversation happening about theming in
> emacs-land right now!
>
> https://lists.gnu.org/archive/html/emacs-devel/2016-02/msg00361.html
Fun, we should keep an eye on it. The Emacs manual currently has its
own CSS, separate from what gendocs.sh does.
Ludo’.
next prev parent reply other threads:[~2016-02-08 20:31 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 [this message]
2016-02-08 21:28 ` Chad Albers
2016-02-08 21:37 ` Thompson, David
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=87io1zueog.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=cwebber@dustycloud.org \
--cc=guile-devel@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).