[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: reftex.el autoloads
From: |
Eli Zaretskii |
Subject: |
Re: reftex.el autoloads |
Date: |
Thu, 10 Dec 2015 18:28:11 +0200 |
> From: address@hidden (Phillip Lord)
> Date: Thu, 10 Dec 2015 11:03:30 +0000
>
> --- a/lisp/textmodes/reftex.el
> +++ b/lisp/textmodes/reftex.el
> @@ -2397,7 +2397,7 @@ reftex-report-bug
> ^L
> ;;; Start of automatically extracted autoloads.
> ^L
> -;;;### (autoloads nil "reftex-auc" "reftex-auc.el"
> "cf606f7918831321cb46f254436dc66e")
> +;;;### (autoloads nil "reftex-auc" "reftex-auc.el"
> "7c0e0b46919f4ceefe1026e31e73ebcd")
> ;;; Generated autoloads from reftex-auc.el
>
> (autoload 'reftex-arg-label "reftex-auc" "\
>
>
> So, it appears that reftex.el is actually partially real source and
> partially generated during the normal build, which doesn't seem a good
> thing to me.
These are autoloads. Several files, reftex.el among them, record
autoloads for their parent packages. Other examples include dired.el,
esh-groups.el, and rmail.el. Grep the Lisp files for
'generated-autoload-file:' (without the quotes), and you will see them
all.
> Am I missing something?
Not sure, but this is normal.
> And is there a good way to fix it?
You mean, for the bisect script? Just "git checkout" the offending
file after the build, that's all.
- reftex.el autoloads, Phillip Lord, 2015/12/10
- Re: reftex.el autoloads, Phillip Lord, 2015/12/10
- Re: reftex.el autoloads, Eli Zaretskii, 2015/12/11
- Re: reftex.el autoloads, Phillip Lord, 2015/12/11
- Re: reftex.el autoloads, Eli Zaretskii, 2015/12/11
- Re: reftex.el autoloads, Phillip Lord, 2015/12/11
- Re: reftex.el autoloads, Glenn Morris, 2015/12/11