unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jean-Christophe Helary <lists@traduction-libre.org>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: make docs
Date: Thu, 23 Dec 2021 01:43:31 +0900	[thread overview]
Message-ID: <6CD7F0A2-6D3A-41B3-92D6-EF36054C2A97@traduction-libre.org> (raw)
In-Reply-To: <CAArVCkQf9T8mAECUKs5PRWBSW74XRVEV1G3qDi3p_DT1vc-EWQ@mail.gmail.com>



> On Dec 23, 2021, at 0:45, Philipp Stephani <p.stephani2@gmail.com> wrote:
> 
> Am Mi., 22. Dez. 2021 um 05:44 Uhr schrieb Jean-Christophe Helary
> <lists@traduction-libre.org>:
>> 
>> Why is it that `make docs` builds the whole code set before building the documentation ?
>> 
> 
> Random guess: Some manuals are written in Org-Mode, and to export them
> to Texinfo you first need to build Org-Mode (and for that you need
> Emacs).

I tried and that doesn't seem to be the issue (although generating the org.texi file does take quite some time).

-- 
Jean-Christophe Helary @brandelune
https://mac4translators.blogspot.com
https://sr.ht/~brandelune/omegat-as-a-book/




  reply	other threads:[~2021-12-22 16:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-22  4:43 make docs Jean-Christophe Helary
2021-12-22 13:29 ` Eli Zaretskii
2021-12-22 14:01   ` Jean-Christophe Helary
2021-12-22 15:45 ` Philipp Stephani
2021-12-22 16:43   ` Jean-Christophe Helary [this message]
2021-12-23  4:34     ` Jean-Christophe Helary
2021-12-23  7:15       ` Eli Zaretskii
2021-12-23  9:00         ` Jean-Christophe Helary
2021-12-23  9:21           ` Eli Zaretskii
2021-12-23 12:44             ` Jean-Christophe Helary
2021-12-23 12:57               ` Philipp Stephani
2021-12-23 13:04                 ` Jean-Christophe Helary
2021-12-23 14:18               ` Eli Zaretskii
2021-12-23 15:08                 ` Jean-Christophe Helary
2021-12-23 16:47 ` Glenn Morris

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/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6CD7F0A2-6D3A-41B3-92D6-EF36054C2A97@traduction-libre.org \
    --to=lists@traduction-libre.org \
    --cc=emacs-devel@gnu.org \
    --cc=p.stephani2@gmail.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).