From: phillip.lord@russet.org.uk (Phillip Lord)
To: Eli Zaretskii <eliz@gnu.org>
Cc: Glenn Morris <rgm@gnu.org>, emacs-devel@gnu.org
Subject: Re: reftex.el autoloads
Date: Fri, 11 Dec 2015 15:35:09 +0000 [thread overview]
Message-ID: <87d1udxaky.fsf@russet.org.uk> (raw)
In-Reply-To: <831tata1mg.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 11 Dec 2015 09:24:55 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: phillip.lord@russet.org.uk (Phillip Lord)
>> Cc: <emacs-devel@gnu.org>
>> Date: Thu, 10 Dec 2015 22:03:32 +0000
>>
>> So, quite a lot of files seem to set generated-autoload-file to
>> loaddefs.el which seems a bit odd (since it's the default).
>
> Only in lisp/cedet/, I think. I'm guessing this is the result of
> integrating CEDET. If you want the details, maybe the CEDET people
> and/or Chong (which did most of the work) could tell you the reasons
> for that. I suggest to look at Git logs and maybe ask them Or maybe
> Glenn (CC'ed) remembers.
It's not a disaster either way.
>> I am not sure why only reftex.el causes me problems -- why not the
>> others, I wonder?
>
> Probably because the range of versions you tried to bisect didn't
> touch the others. It obviously depends on which files whose autoloads
> are there are modified by the commits you are bisecting.
Yes, I guess that is true.
>> Also, the changed line is actually this...
>>
>> >> +;;;### (autoloads nil "reftex-auc" "reftex-auc.el" "7c0e0b46919f4ceefe1026e31e73ebcd")
>>
>> which is a comment. I don't know what this line does in the autoload
>> process.
>
> It's documented in the ELisp manual. Which parts are unclear?
I did re-read the elisp manual, of course, and I can't find anything
which documents this; it describes comments in files to be autoloaded,
but not the autoloads. I tracked the source code, and it's inserted by
`autoload-insert-section-header'.
Deep in the bowels of autoload.el, there is a call to this which is
documented like this:
;; MD5 checksums are much better because they do not
;; change unless the file changes (so they'll be
;; equal on two different systems and will change
;; less often than time-stamps, thus leading to fewer
;; unneeded changes causing spurious conflicts), but
;; using time-stamps is a very useful optimization,
;; so we use time-stamps for the main autoloads file
;; (loaddefs.el) where we have special ways to
;; circumvent the "random change problem", and MD5
;; checksum in secondary autoload files where we do
;; not need the time-stamp optimization because it is
;; already provided by the primary autoloads file.
So, it's a checksum (not a git commit which was my first thought) of the
file contents (except in loaddefs.el when it's a timestamp). So it will
update whenever reftex-auc changes whether the autoloads need to change
or not.
Phil
next prev parent reply other threads:[~2015-12-11 15:35 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 11:03 reftex.el autoloads Phillip Lord
2015-12-10 14:48 ` Artur Malabarba
2015-12-10 16:28 ` Eli Zaretskii
2015-12-10 18:52 ` Paul Eggert
2015-12-10 22:07 ` Phillip Lord
2015-12-11 7:26 ` Eli Zaretskii
2015-12-11 15:38 ` Phillip Lord
2015-12-10 22:03 ` Phillip Lord
2015-12-11 7:24 ` Eli Zaretskii
2015-12-11 15:35 ` Phillip Lord [this message]
2015-12-11 16:18 ` Eli Zaretskii
2015-12-11 17:08 ` Phillip Lord
2015-12-11 17:46 ` Glenn Morris
2015-12-11 18:20 ` Phillip Lord
2015-12-11 20:03 ` Paul Eggert
2015-12-12 18:24 ` Phillip Lord
2015-12-12 18:42 ` Eli Zaretskii
2015-12-12 18:56 ` Phillip Lord
2015-12-12 19:09 ` Eli Zaretskii
2015-12-12 21:15 ` Phillip Lord
2015-12-13 3:33 ` Eli Zaretskii
2015-12-13 20:33 ` Phillip Lord
2015-12-13 21:50 ` Glenn Morris
2015-12-13 22:11 ` Phillip Lord
2015-12-15 19:33 ` Glenn Morris
2015-12-16 17:15 ` Phillip Lord
2015-12-17 2:15 ` Glenn Morris
2015-12-17 3:42 ` Eli Zaretskii
2015-12-17 16:07 ` John Wiegley
2015-12-17 21:31 ` Phillip Lord
2015-12-18 16:39 ` Glenn Morris
2015-12-18 17:12 ` Paul Eggert
2015-12-18 20:55 ` Phillip Lord
2015-12-18 21:27 ` Eli Zaretskii
2015-12-18 21:51 ` Phillip Lord
2015-12-19 7:29 ` Eli Zaretskii
2015-12-18 22:05 ` Phillip Lord
2015-12-19 7:31 ` Eli Zaretskii
2015-12-19 13:24 ` Phillip Lord
2015-12-20 12:41 ` Phillip Lord
2015-12-20 15:59 ` Eli Zaretskii
2015-12-20 18:41 ` Phillip Lord
2015-12-20 18:37 ` Glenn Morris
2015-12-20 23:04 ` Phillip Lord
2015-12-21 0:24 ` Glenn Morris
2015-12-21 10:32 ` Phillip Lord
2015-12-22 10:55 ` Phillip Lord
2015-12-21 6:45 ` martin rudalics
2015-12-21 10:31 ` Phillip Lord
2015-12-18 20:45 ` Phillip Lord
2015-12-18 21:22 ` Phillip Lord
2015-12-20 18:41 ` Glenn Morris
2015-12-20 19:05 ` Eli Zaretskii
2015-12-21 0:22 ` Glenn Morris
2015-12-20 23:15 ` Phillip Lord
2015-12-21 0:29 ` Glenn Morris
2015-12-21 10:52 ` Phillip Lord
2015-12-17 5:57 ` Paul Eggert
2015-12-17 12:07 ` Phillip Lord
2015-12-11 17:34 ` David Engster
2015-12-11 17:39 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d1udxaky.fsf@russet.org.uk \
--to=phillip.lord@russet.org.uk \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rgm@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 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.