unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: emacs-devel@gnu.org
Subject: Re: Reworking loaddefs.el generation
Date: Wed, 01 Jun 2022 14:40:44 +0300	[thread overview]
Message-ID: <83fskoharn.fsf@gnu.org> (raw)
In-Reply-To: <87zgix2k29.fsf@gnus.org> (message from Lars Ingebrigtsen on Wed,  01 Jun 2022 04:29:02 +0200)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: emacs-devel@gnu.org
> Date: Wed, 01 Jun 2022 04:29:02 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > I see it starting from 10%, and it takes longer than typical updates
> > before the change, which usually would just show 90% and then "done".
> 
> In which cases?  If I
> 
> touch .git/logs/HEAD lisp/gnus/gnus.el; time make -j4
> 
> it just says
> 
>   INFO     Scraping files for loaddefs... 
>   INFO     Scraping files for loaddefs...done
>   GEN      loaddefs.el

I see this with the current master:

  $ touch lisp/array.el .git/logs/HEAD
  $ make -j4
  [...]
    GEN      loaddefs.el
    INFO     Scraping files for loaddefs...
    INFO     Scraping files for loaddefs...26%
    INFO     Scraping files for loaddefs...53%
    INFO     Scraping files for loaddefs...81%
    INFO     Scraping files for loaddefs...done
    GEN      loaddefs.el

Why so much "scraping" lines for just one file modified?

And the example which was before my eyes when I wrote the above was
actually this:

    ELC      ../lisp/minibuffer.elc
    ELC      ../lisp/newcomment.elc
    ELC      ../lisp/simple.elc
  [...]
    GEN      loaddefs.el
    INFO     Scraping files for loaddefs...
    INFO     Scraping files for loaddefs...10%
    INFO     Scraping files for loaddefs...20%
    INFO     Scraping files for loaddefs...30%
    INFO     Scraping files for loaddefs...40%
    INFO     Scraping files for loaddefs...50%
    INFO     Scraping files for loaddefs...60%
    INFO     Scraping files for loaddefs...70%
    INFO     Scraping files for loaddefs...80%
    INFO     Scraping files for loaddefs...90%
    INFO     Scraping files for loaddefs...100%
    INFO     Scraping files for loaddefs...done
    GEN      textmodes/reftex-loaddefs.el
    GEN      textmodes/texinfo-loaddefs.el
    GEN      org/org-loaddefs.el
    GEN      net/tramp-loaddefs.el
    GEN      mh-e/mh-loaddefs.el
    GEN      mail/rmail-loaddefs.el
    GEN      eshell/esh-groups.el
    GEN      erc/erc-loaddefs.el
    GEN      emacs-lisp/eieio-loaddefs.el
    GEN      emacs-lisp/cl-loaddefs.el
    GEN      cedet/srecode/loaddefs.el
    GEN      cedet/semantic/loaddefs.el
    GEN      cedet/ede/loaddefs.el
    GEN      calendar/diary-loaddefs.el
    GEN      calendar/holiday-loaddefs.el
    GEN      calendar/cal-loaddefs.el
    GEN      calc/calc-loaddefs.el
    GEN      ps-print-loaddefs.el
    GEN      ibuffer-loaddefs.el
    GEN      htmlfontify-loaddefs.el
    GEN      dired-loaddefs.el
    GEN      loaddefs.el
  [...]
    ELC      bookmark.elc
    ELC      emacs-lisp/loaddefs-gen.elc
    ELC      textmodes/tex-mode.elc

IOW, only 6 Lisp files and none of the C files were modified, and yet
all the *loaddefs.el files were regenerated from scratch.  (That was
yesterday at 22:40 UTC+3, so maybe you changed something since then.)



  reply	other threads:[~2022-06-01 11:40 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-27 10:53 Reworking loaddefs.el generation Lars Ingebrigtsen
2022-05-27 12:03 ` Andreas Schwab
2022-05-27 12:17   ` Lars Ingebrigtsen
2022-05-27 12:43 ` Stefan Monnier
2022-05-27 13:00   ` Lars Ingebrigtsen
2022-05-31 16:10 ` Lars Ingebrigtsen
2022-05-31 16:33   ` Lars Ingebrigtsen
2022-05-31 16:53     ` Lars Ingebrigtsen
2022-05-31 17:32       ` Eli Zaretskii
2022-05-31 17:40         ` Lars Ingebrigtsen
2022-05-31 18:09       ` Lars Ingebrigtsen
2022-05-31 19:24         ` Eli Zaretskii
2022-05-31 19:33           ` Lars Ingebrigtsen
2022-06-01  2:26             ` Eli Zaretskii
2022-06-01  2:29               ` Lars Ingebrigtsen
2022-06-01 11:40                 ` Eli Zaretskii [this message]
2022-06-01 12:13                   ` Lars Ingebrigtsen
2022-06-01 19:02                     ` Eli Zaretskii
2022-06-02  9:14                       ` Lars Ingebrigtsen
2022-05-31 18:44 ` Alan Mackenzie
2022-05-31 18:47   ` Lars Ingebrigtsen
2022-06-01  3:55     ` Lars Ingebrigtsen
2022-06-01  5:43       ` Lars Ingebrigtsen
2022-06-01 11:16         ` Lars Ingebrigtsen
2022-06-01 11:26           ` Lars Ingebrigtsen
2022-06-01 12:00           ` Andreas Schwab
2022-06-01 12:10             ` Lars Ingebrigtsen
2022-06-01 14:23             ` Lars Ingebrigtsen
2022-06-01 11:47       ` Stefan Monnier
2022-06-01 12:09         ` Lars Ingebrigtsen
2022-05-31 19:04   ` Stefan Monnier
2022-06-01  5:13     ` Lars Ingebrigtsen
2022-06-01 11:07       ` Eli Zaretskii
2022-06-01 12:29         ` Lars Ingebrigtsen
2022-05-31 19:00 ` Lars Ingebrigtsen
2022-05-31 19:12   ` Lars Ingebrigtsen

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=83fskoharn.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.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).