From mboxrd@z Thu Jan 1 00:00:00 1970 From: Laura Lazzati Subject: Re: Trying to make texinfo patch Date: Mon, 5 Nov 2018 22:44:02 -0300 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="00000000000016bb480579f5252f" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:47058) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gJqQC-0003cR-Is for guix-devel@gnu.org; Mon, 05 Nov 2018 20:44:49 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gJqQB-0002m0-Gz for guix-devel@gnu.org; Mon, 05 Nov 2018 20:44:48 -0500 In-Reply-To: List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: =?UTF-8?Q?G=C3=A1bor_Boskovits?= Cc: Guix-devel , Ricardo Wurmus --00000000000016bb480579f5252f Content-Type: text/plain; charset="UTF-8" > I don't know if we currently have a top level Makefile target to build > the manual only, but simply make-ing in the source tree rebuilds the > manual. I believe that is the simplest > way to test changes. > I tried to explain what I did on IRC. In the end I just git pulled and got the new version of the guix.texi file. Ran make again in the source tree - helped me to recall some useful Makefile concepts. And added just the few cindex again, they are not many, but to check that I learned texinfo. Then, since in guix.info website I had the full html version, ran: makeinfo --html --nosplit guix.texi and got a similar html file that looked similar to the original one, nut with the index entries updated. And I don't know if I should write this in guix-devel, there is a bug list - it's almost my time to go to bed, but I recall seing it - where I was mentioning that in guix.info site the references to documentation have html_node in their path and they return a 404 not found when clicking them. Tomorrow I will try to send the patch. I have some questions to ask you: 1) I got an Ourteachy reminder about recording my Application form. I guess it was just a reminder, but please let me know if it you got it. 2) I was suggested to have at least for a my foreing distro and guix package manager an aws account, in case something happens to my computer. I don't know if it is accepted by the community. 3) Is it OK if I write daily telling you what I will be doing/ did that day, and what I am learning if the number of contributions don't count that much? Maybe it is more useful that. Regards! Laura --00000000000016bb480579f5252f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

I don't know if we currently have a top level Makefile target to build<= br> the manual only, but simply make-ing in the source tree rebuilds the
manual. I believe that is the simplest
way to test changes.
I tried to explain what I did on = IRC. In the end I just git pulled and got the new version of the guix.texi = file.
Ran make again in the source tree - helped me to recall som= e useful Makefile concepts. And added just the few cindex again, they are n= ot many, but to check that I learned texinfo.
Then, since in guix.info website I had the full html version,= ran:
makeinfo --html --nosplit guix.texi and got a similar html = file that looked similar to the original one, nut with the index entries up= dated.
And I don't know if I should write this in guix-d= evel, there is a bug list - it's almost my time to go to bed, but I rec= all seing it=C2=A0 - where I was mentioning that in guix.info site the references to documentation have html_node in = their path and they return a 404 not found when clicking them. Tomorrow I w= ill try to send the patch.
I have some questions to ask you:
=
1) I got an Ourteachy reminder about recording my Application fo= rm. I guess it was just a reminder, but please let me know if it you got it= .
2) I was suggested to have at least for a my foreing distr= o and guix package manager an aws account, in case something happens to my = computer. I don't know if it is accepted by the community.
3)= Is it OK if I write daily telling you what I will be doing/ did that day, = and what I am learning if the number of contributions don't count that = much? Maybe it is more useful that.

Regards!<= /div>
Laura

=C2=A0
=C2=A0
<= /div>
--00000000000016bb480579f5252f--