From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: Upgrade org-mode over a older distribution version
Date: Thu, 31 May 2012 21:32:51 +0200 [thread overview]
Message-ID: <87ipfctacc.fsf@Rainer.invalid> (raw)
In-Reply-To: CA+G3xFhAQC29vUXrzZS0_di-8SVCf-vJ4pBBVYvEc=HVS-eczQ@mail.gmail.com
Michael Baum writes:
> Many thanks. I was afraid of something like that. So the idea is that
> a set or org-mode files under site-lisp takes precedence over the
> built-in files and that's how emacs knows which ones to run?
Emacs will always load the file(s) it finds first in load-path, so you
can do anything by setting it up accordingly. By default load-path is
set up so that things in site-lisp are seen before
<emacs-version>/site-lisp before <emacs-version>/lisp. So if you keep
that structure (and Linux distributions generally do), it becomes easy
to keep updated packages there.
BTW, after you've done this, you will need a (require 'org-install) in
your emacs startup files. With the Emacs builtin org it's not strictly
necessary (but harmless if present).
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
next prev parent reply other threads:[~2012-05-31 19:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-31 18:42 Upgrade org-mode over a older distribution version Michael Baum
2012-05-31 18:57 ` Achim Gratz
2012-05-31 19:19 ` Michael Baum
2012-05-31 19:32 ` Achim Gratz [this message]
2012-05-31 20:01 ` Crash in "GNU Emacs 24.0.97.1 (i386-mingw-nt5.1.2600) of 2012-05-17 on MARVIN" when jumpin to end of long lines of org-mode file Rainer Stengele
2012-06-01 12:53 ` Bastien
2012-06-01 11:31 ` Rainer Stengele
2012-06-01 14:41 ` Nick Dokos
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=87ipfctacc.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).