From: Eric Schulte <eric.schulte@gmx.com>
To: Carsten Mattner <carstenmattner@googlemail.com>
Cc: Dave Abrahams <dave@boostpro.com>, Bastien <bzg@altern.org>,
Chong Yidong <cyd@gnu.org>,
emacs-devel@gnu.org
Subject: Re: Periodical releases
Date: Thu, 05 Jan 2012 07:18:33 -0700 [thread overview]
Message-ID: <878vlmb5by.fsf@gmx.com> (raw)
In-Reply-To: CACY+HvqMw+VFKiPQtvyizrTBP_0RKwa0B1smO2y15=HBT3c0OA@mail.gmail.com
Carsten Mattner <carstenmattner@googlemail.com> writes:
> On Thu, Jan 5, 2012 at 10:31 AM, Bastien <bzg@altern.org> wrote:
>> 2) I will probably release Org 8.0 before the end of the feature freeze
>> (say march or april). Not having it in Emacs 24.1 is not such a big
>> deal, agreed, but it creates a situation where people often install
>> Org on top of the one that comes with Emacs, which doesn't feel
>> optimal and leads to many questions, because of conflicting installs.
>
> Out of curiosity. If I have 24.1 with Org 7.x and to use Org latest
> I put that in ~/.emacs.d/<somewhere>, is there some potential
> ambiguity/conflict/version-clash/mixup going on if I add that
> local dir to the load path? Do I have to use some unknown-to-me
> (prepend-to-load-path path)? I know that Vim has ~/.vim/* first in the
> path list. What's it for Emacs?
The `add-to-list' function will place any new directory at the front of
your load path. In general adding the new version of Org-mode to your
load path, loading or requiring org, and then calling the `org-reload'
function should be sufficient. For more information see [1].
However, when an older version of Org-mode (e.g., one shipped with
Emacs) is loaded first it defines all Org-mode variables. Subsequent
versions of Org-mode will not update the values of these variables as a
defvar of an existing variable does not change its value. This
frequently leads to buggy behavior. This point would argue for
migration of Org-mode to ELPA in future releases.
Best -- Eric
Footnotes:
[1] http://orgmode.org/worg/org-faq.html#Keeping-current
--
Eric Schulte
http://cs.unm.edu/~eschulte/
next prev parent reply other threads:[~2012-01-05 14:18 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-31 12:00 Periodical releases Carsten Mattner
2012-01-01 22:41 ` Stefan Monnier
2012-01-02 10:40 ` Carsten Mattner
2012-01-02 11:36 ` Eli Zaretskii
2012-01-02 12:57 ` Carsten Mattner
2012-01-02 17:31 ` Eli Zaretskii
2012-01-02 19:05 ` Drew Adams
2012-01-02 19:54 ` chad
2012-01-02 21:36 ` Carsten Mattner
2012-01-02 20:29 ` Eric Schulte
2012-01-02 21:31 ` Carsten Mattner
2012-01-02 20:41 ` Lluís
2012-01-02 21:23 ` Carsten Mattner
2012-01-02 22:14 ` Drew Adams
2012-01-02 22:27 ` Carsten Mattner
2012-01-05 2:34 ` Dave Abrahams
2012-01-05 2:58 ` Chong Yidong
2012-01-05 3:36 ` Dave Abrahams
2012-01-05 4:23 ` Óscar Fuentes
2012-01-05 13:25 ` Eli Zaretskii
2012-01-05 13:41 ` Dave Abrahams
2012-01-05 9:31 ` Bastien
2012-01-05 10:11 ` Leo
2012-01-05 11:31 ` Carsten Mattner
2012-01-05 12:56 ` Jambunathan K
2012-01-05 14:00 ` Leo
2012-01-05 14:30 ` Jambunathan K
2012-01-05 11:28 ` Carsten Mattner
2012-01-05 14:18 ` Eric Schulte [this message]
2012-01-05 11:33 ` Carsten Mattner
2012-01-05 5:43 ` Eli Zaretskii
2012-01-05 12:20 ` Dave Abrahams
2012-01-05 15:34 ` Drew Adams
2012-01-03 22:23 ` Stefan Monnier
2012-01-03 18:18 ` What's in a feature? (was: Periodical releases) Bastien
2012-01-04 3:24 ` Stephen J. Turnbull
2012-01-04 10:03 ` What's in a feature? Bastien
2012-01-04 12:43 ` Juanma Barranquero
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878vlmb5by.fsf@gmx.com \
--to=eric.schulte@gmx.com \
--cc=bzg@altern.org \
--cc=carstenmattner@googlemail.com \
--cc=cyd@gnu.org \
--cc=dave@boostpro.com \
--cc=emacs-devel@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.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).