From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: Web site bug
Date: Mon, 29 Oct 2012 08:29:14 +0100 [thread overview]
Message-ID: <877gq9wxbp.fsf@Rainer.invalid> (raw)
In-Reply-To: 87objllq8x.fsf@bzg.ath.cx
Bastien writes:
> Can you point at an actual reproducible and simple bug with
> the current way Org defines autoloads?
After the introduction of org-loaddefs, the autoloads should be
extracted into two files and only the first is supposed to be loaded
before org is actually used and the second, org-loaddefs, is supposed to
be loaded by Org itself. But when using a standalone Org, that first
file doesn't exist and there's no mechanism for the generated autoloads
(all in org-loaddefs) to be loaded before Org is used.
You suggest that in a standalone installation the user doesn't need to
do anything by way of customization: that's a bug, because the autoloads
in org-loaddefs for the standalone Org are not present _at all_ in that
situation. That there may be some autoloads present from another Org
version (from Emacs) that by accident may point to a file that will then
cause Org to be loaded anyway doesn't make this bug go away.
Standalone Org needs a file separate from org-loaddefs to collect the
autoload definitions into that will be loaded on startup. For Emacs,
this is loaddefs; for package manager, this is org-autoloads; for Org
standalone, I posit that we should keep org-install. If we keep a
different system of how to handle autoloads depending on the type of
installation, then it will be impossible to test that everything works
correctly[1], not to mention the confusion that this discussion so amply
demonstrates.
[1] For instance, any first-level autoloaded function that somehow calls
into these files:
ob, ob-keys, ob-lob, ob-tangle, org-archive, org-ascii, org-attach,
org-bbdb, org-clock, org-datetree, org-docbook, org-element, org-exp,
org-feed, org-footnote, org-freemind, org-html, org-icalendar, org-id,
org-indent, org-irc, org-latex, org-lparse, org-mobile, org-odt,
org-plot, org-publish, org-remember, org-table, org-taskjuggler,
org-timer, org-xoxo
needs to make sure that org-loaddefs has been loaded, which currently
only happens in org, but I have not been able to ascertain that each
codepath to one of these functions will actually go through it.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
next prev parent reply other threads:[~2012-10-29 7:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 20:36 Web site bug Simon Thum
2012-10-24 22:42 ` Bastien
2012-10-26 19:57 ` Simon Thum
2012-10-27 7:33 ` Bastien
2012-10-27 8:54 ` Sebastien Vauban
2012-10-27 9:06 ` Bastien
2012-10-28 7:36 ` Achim Gratz
2012-10-28 10:29 ` Bastien
2012-10-28 16:12 ` Achim Gratz
2012-10-29 6:57 ` Bastien
2012-10-29 7:29 ` Achim Gratz [this message]
2012-10-29 7:33 ` Bastien
2012-10-29 7:48 ` Achim Gratz
2012-10-29 8:56 ` Eric S Fraga
2012-10-29 6:56 ` Bastien
2012-10-29 7:02 ` Achim Gratz
2012-10-29 7:07 ` Bastien
2012-10-27 16:15 ` Simon Thum
2012-10-27 19:37 ` Bastien
2012-10-27 8:01 ` Achim Gratz
2012-10-27 8:28 ` Bastien
2012-10-27 11:11 ` Achim Gratz
-- strict thread matches above, loose matches on Subject: below --
2010-07-20 16:11 web " Robert Klein
2010-07-25 16:26 ` David Maus
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877gq9wxbp.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=emacs-orgmode@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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.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).