From: Federico Beffa <beffa@ieee.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH 5/6] gnu: mit-scheme: Generate and install documentation.
Date: Sat, 9 Jan 2016 23:32:28 +0100 [thread overview]
Message-ID: <CAKrPhPMZ+kO5gQC7=bw_BcwjTeTugsFETejcxwD3mq6GpMo9ZQ@mail.gmail.com> (raw)
In-Reply-To: <87vb72a924.fsf@gnu.org>
On Sat, Jan 9, 2016 at 7:42 PM, Ludovic Courtès <ludo@gnu.org> wrote:
> Federico Beffa <beffa@ieee.org> skribis:
>> MIT Scheme is a complex system and without the documentation it's not
>> possible to use it proficiently.
>
> Agreed, I didn’t mean to imply we should give up on documentation.
>
> I just realized that its documentation is in Texinfo format. What about
> simply installing the Info format like we do for other GNU packages, and
> not the PDF/PS/DVI version?
Texinfo is great for looking up pieces of information in a reference
manual. However, when it comes to reading a sizable part, I much prefer
PDFs with a much superior graphic quality and scaling capability and
would like to keep it (my eyes aren't in great conditions). I think we
can drop PS. DVI is not installed. HTML is required by
'emacs-mit-scheme-doc'.
Regards,
Fede
next prev parent reply other threads:[~2016-01-09 22:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-30 17:33 [PATCH 5/6] gnu: mit-scheme: Generate and install documentation Federico Beffa
2016-01-05 22:13 ` Ludovic Courtès
2016-01-09 10:28 ` Federico Beffa
2016-01-09 18:42 ` Ludovic Courtès
2016-01-09 22:32 ` Federico Beffa [this message]
2016-01-10 18:50 ` Ludovic Courtès
2016-01-10 21:19 ` Federico Beffa
2016-01-10 23:14 ` Mathieu Lirzin
2016-01-11 8:20 ` Federico Beffa
2016-01-11 9:09 ` Ludovic Courtès
2016-01-11 11:58 ` Federico Beffa
2016-01-11 19:06 ` Leo Famulari
2016-01-12 7:46 ` Federico Beffa
2016-01-11 20:47 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAKrPhPMZ+kO5gQC7=bw_BcwjTeTugsFETejcxwD3mq6GpMo9ZQ@mail.gmail.com' \
--to=beffa@ieee.org \
--cc=guix-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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.