From: Jean-Christophe Helary <lists@traduction-libre.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: make docs
Date: Wed, 22 Dec 2021 23:01:01 +0900 [thread overview]
Message-ID: <8B5E97A5-FF2B-4303-8AFA-545831C18874@traduction-libre.org> (raw)
In-Reply-To: <83k0fwydhx.fsf@gnu.org>
> On Dec 22, 2021, at 22:29, Eli Zaretskii <eliz@gnu.org> wrote:
>
>> From: Jean-Christophe Helary <lists@traduction-libre.org>
>> Date: Wed, 22 Dec 2021 13:43:28 +0900
>>
>> Why is it that `make docs` builds the whole code set before building the documentation ?
>
> It does? How did you see that?
I created a new branche to check the case sensitive setting that Gavin suggested I test and I applied my Makefile patch to add my local .css etc. reconfigured and when I hit Enter after `make docs` I got the whole thing rebuilt (including the .elc compilation, etc.)
> Can you show what happens when you try that on your system?
Now that I've built the doc once that doesn't happen. I'll try to reproduce, but I seem to remember that it's not the first time I'm surprised by that.
--
Jean-Christophe Helary @brandelune
https://mac4translators.blogspot.com
https://sr.ht/~brandelune/omegat-as-a-book/
next prev parent reply other threads:[~2021-12-22 14:01 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 [this message]
2021-12-22 15:45 ` Philipp Stephani
2021-12-22 16:43 ` Jean-Christophe Helary
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=8B5E97A5-FF2B-4303-8AFA-545831C18874@traduction-libre.org \
--to=lists@traduction-libre.org \
--cc=eliz@gnu.org \
--cc=emacs-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.
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).