From: Glenn Morris <rgm@gnu.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: "Clément Pit--Claudel" <clement.pitclaudel@live.com>,
23692@debbugs.gnu.org
Subject: bug#23692: 25.1.50; Package.el gets confused if file has no autoloads (could be a bug in update-directory-autoloads)
Date: Mon, 13 Jun 2016 14:33:49 -0400 [thread overview]
Message-ID: <vur3c1aqgi.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <jwva8ivyw0m.fsf-monnier+emacsbugs@gnu.org> (Stefan Monnier's message of "Wed, 08 Jun 2016 21:47:04 -0400")
Stefan Monnier wrote:
> - (when changed
> + (if (not changed)
> + (set-buffer-modified-p nil)
I guess that will work. Some vague thoughts:
i) I guess now autoload will sometimes not create any output file.
Does that matter?
ii) I wonder what this means for reproducibility of the loaddefs file.
IIRC When building Emacs itself, the loaddefs file can change if you:
make -j8 bootstrap; make -C lisp autoloads
due to changes in "files with no autoloads" section owing to generated
files being created in parallel with loaddefs.el (this is really a
failure in dependency tracking for loaddefs, but it's harmless).
But it does finally converge to a fixed state. Will it still do so if
the loaddefs file sometimes isn't written?
iii) Would applying a move-if-change style logic be better?
next prev parent reply other threads:[~2016-06-13 18:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-03 22:03 bug#23692: 25.1.50; Package.el gets confused if file has no autoloads (could be a bug in update-directory-autoloads) Clément Pit--Claudel
2016-06-03 22:50 ` Glenn Morris
2016-06-04 4:34 ` Clément Pit--Claudel
2016-06-06 17:24 ` Glenn Morris
2016-06-09 1:47 ` Stefan Monnier
2016-06-13 18:33 ` Glenn Morris [this message]
2016-06-14 0:40 ` Stefan Monnier
2016-10-10 9:56 ` Eli Zaretskii
2016-10-11 19:56 ` Stefan Monnier
2016-10-11 20:54 ` Eli Zaretskii
2016-06-13 22:17 ` Clément Pit--Claudel
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=vur3c1aqgi.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=23692@debbugs.gnu.org \
--cc=clement.pitclaudel@live.com \
--cc=monnier@IRO.UMontreal.CA \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.