GNU bug report logs - #27581
26.0.50; Error while compiling new Org code

Previous Next

Full log

Message #34 received at 27581-done <at> debbugs.gnu.org (full text, mbox):

From: Stefan Kangas <stefan <at> marxist.se>
To: Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: 27581-done <at> debbugs.gnu.org, npostavs <at> users.sourceforge.net
Subject: Re: bug#27581: 26.0.50; Error while compiling new Org code
Date: Thu, 1 Oct 2020 04:59:14 -0700

Stefan Kangas <stefan <at> marxist.se> writes:

> Stefan Monnier <monnier <at> IRO.UMontreal.CA> writes:
>
>>> I think I hit this, and doing 'make autoloads' fixed it.
>>
>> Duh, indeed, so the `declare-function` should be removed.
>> Remains my question about the use of eval-after-load.
>
> Stefan Monnier <monnier <at> IRO.UMontreal.CA> writes:
>
>> So it's triggered during the evaluation of org-compat.el's after-load:
>>
>>     (eval-after-load 'org
>>       '(progn
>>          (org-link-set-parameters "file+emacs") ;since Org 9.0
>>          (org-link-set-parameters "file+sys"))) ;since Org 9.0
>>
>> There's a (declare-function org-element-update-syntax ...) in org.el but
>> it looks like org-element is not loaded in this case.
>>
>> Not sure which is the right fix, but I do wonder why have this
>> eval-after-load in org-compat.el instead of simply moving the code to
>> org.el: eval-after-load is normally only used when we need to add code
>> to a file that's not under our control.
>
> I can't find that eval-after-load in org-compat.el, so I guess this has
> been fixed in the three years since this was reported.
>
> I guess this should be closed then?

More information was requested, but none was given within 7 weeks, so
I'm closing this bug.  If this is still an issue, please reply to this
email (use "Reply to all" in your email client) and we can reopen the
bug report.

Best regards,
Stefan Kangas

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.