From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: The Org Package
Date: Wed, 16 Apr 2014 18:35:39 +0200 [thread overview]
Message-ID: <87r44x1bc4.fsf@Rainer.invalid> (raw)
In-Reply-To: 8661mayw9t.fsf@gmail.com
David Masterson writes:
> Hmmm. I would think that this process might work as well:
>
> 1. Start with "emacs -Q"
This fails with some older versions of Emacs since these had a bug where
parts of the init scripts were processed even when you said explicitly
that they shouldn't be read.
> 2. Bring up the Emacs Packages list
> 3. Mark the "available" org for "U"pgrade
> 4. Execute the upgrade
> 5. Restart Emacs
With the version of Emacs you have that should work, yes.
> The only question is what about the built-in Org?
Leave it alone. Unless you _are_ planning to build your own Emacs
without it, nothing can be done that might not lead to hard to find
problems later on. If you're willing to experiment, look at
testing/org-batch-test-init.el
for how to get rid of the pre-installed Org (or at least those parts
that I know about). Obviously it works in batch mode, otherwise we'd
have tons of complaints about it; but I can't really say if there might
be problems with a full-fledged GUI Emacs session.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
DIY Stuff:
http://Synth.Stromeko.net/DIY.html
next prev parent reply other threads:[~2014-04-16 16:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-12 2:32 The Org Package David Masterson
2014-04-12 2:39 ` John Hendy
2014-04-12 4:10 ` David Masterson
2014-04-12 6:01 ` Jacek Generowicz
2014-04-12 20:07 ` John Hendy
2014-04-15 2:05 ` adam
2014-04-13 1:41 ` Grant Rettke
2014-04-13 7:05 ` Achim Gratz
2014-04-13 7:14 ` Nicolas Richard
2014-04-13 22:27 ` David Masterson
2014-04-14 0:15 ` Thomas S. Dye
2014-04-16 0:04 ` David Masterson
2014-04-16 16:35 ` Achim Gratz [this message]
2014-04-14 16:16 ` Achim Gratz
2014-04-17 11:38 ` Bastien
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=87r44x1bc4.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).