From: Catonano <catonano@gmail.com>
To: Catonano <catonano@gmail.com>, "Ludovic Courtès" <ludo@gnu.org>,
help-guix <help-guix@gnu.org>
Subject: Re: Hwo to debug and teacking builds?
Date: Tue, 28 Mar 2017 20:11:14 +0200 [thread overview]
Message-ID: <CAJ98PDxF535X6xR-Np5mhf8f4goo4PU3y6z3QYdf2GE+qsguCg@mail.gmail.com> (raw)
In-Reply-To: <20170328160754.vsmzshiwlqb322av@abyayala>
[-- Attachment #1: Type: text/plain, Size: 1116 bytes --]
2017-03-28 18:07 GMT+02:00 ng0 <contact.ng0@cryptolab.net>:
> Catonano transcribed 4.3K bytes:
>
>
>
> > Which is the source file ?
>
> doc/guix.texi
>
>
Thank you.
I'd like to ask something about Emacs. A bit off topic but not that much.
I remember seeing an Emacs package that displays a preview of the whole
document (buffer ?) in a small region of the window (frame ?)
So that you can know which portion of the document is currently displayed
Gedit, like many editors, does this, it's showed here (the small square on
the right)
ctrlv.in/938108
Too bad that I can't remember how it was called and I couldn't find
anything related on line
If anyone has a hint, I'd appreciate that
It'd be helpful in browsing the guix.texi file that's quite large.
> How do I compile it ?
>
> I never got anything else than html to build with make of guix, (make
> doc/guix.html)..
>
it's not super obvious. I know how texi2pdf etc works,
> but this should at least be listed somewhere other than the Makefile.
>
It definitely should be. I had no idea.
And I wouldn't know what to look for in the Makefile
Thanks again
[-- Attachment #2: Type: text/html, Size: 2230 bytes --]
next prev parent reply other threads:[~2017-03-28 18:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 9:16 Hwo to debug and teacking builds? Hartmut Goebel
2017-03-28 9:52 ` Ludovic Courtès
2017-03-28 13:45 ` Catonano
2017-03-28 16:07 ` ng0
2017-03-28 18:11 ` Catonano [this message]
2017-03-28 18:24 ` ng0
2017-04-10 6:39 ` Ricardo Wurmus
2017-04-10 7:19 ` Catonano
2017-03-29 6:10 ` Chris Marusich
2017-03-29 10:36 ` Catonano
2017-04-11 14:15 ` myglc2
2017-04-11 15:40 ` Chris Marusich
2017-04-11 16:36 ` Hartmut Goebel
2017-04-11 19:01 ` myglc2
2017-04-13 1:32 ` Chris Marusich
2017-03-28 15:58 ` Hartmut Goebel
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=CAJ98PDxF535X6xR-Np5mhf8f4goo4PU3y6z3QYdf2GE+qsguCg@mail.gmail.com \
--to=catonano@gmail.com \
--cc=help-guix@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).