From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: Web site bug
Date: Sat, 27 Oct 2012 10:01:18 +0200 [thread overview]
Message-ID: <87fw50cpip.fsf@Rainer.invalid> (raw)
In-Reply-To: 508AEB33.8050205@gmx.de
Simon Thum writes:
> Which is the recommended thing in what setup? If ELPA needs not even
> org, which AFAIK is not the case, then what? And what about git
> installs?
>
> I guess I'm wholly confused now.
You never needed to do anything extra for using Org as it comes with
Emacs, the autoloads are automatically loaded from loaddefs.el. The
distribution contained an empty org-install for ease of transition.
The package manager generates and loads its own autoload file
(org-autoloads.el, it also re-generates org-loaddefs.el in 7.9.2 and
later), so again you don't need to do anything extra there.
If you were using a seperate Org install (from tarball or Git),
org-install needed to be loaded for getting the correct autoload
definitions. With the introduction of org-loaddefs, things have become
muddled: in Emacs and with package manager, org-loaddefs only contains
those autoload definitions that become available _after_ Org has been
loaded, and the generally visible autoloads come from either loaddefs.el
or org-autoloads.el respectively. The standalone Org does not have a
second autoload file for these first level autoloads, so they are rolled
into org-loaddefs as well. As a result, you must now load org (which in
turn loads org-loaddefs). I still think it would be better if Org had a
separate first-level autoloads file that must be explicitly required by
the user (and it would probably be easiest if it was still called
org-install).
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
next prev parent reply other threads:[~2012-10-27 8:01 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
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 [this message]
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=87fw50cpip.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).