emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: org 9.2.6 and org 9.1.9
Date: Tue, 26 Nov 2019 14:15:26 -0500	[thread overview]
Message-ID: <874kyqcuup.fsf@alphaville.usersys.redhat.com> (raw)
In-Reply-To: <7D2A3D8D-CB71-4B0D-8839-9633BD9F9C4B@traduction-libre.org>

Jean-Christophe Helary <jean.christophe.helary@traduction-libre.org> writes:

> org 9.1.9 is a built-in
> but org 9.2.6 comes as a dependency to some packages and having both installed creates conflicts.

What conflicts are you seeing? I have the built-in 9.1.9 org that
comes with emacs but I run (close to) latest master and I see no
problems: the only thing I do is to set my load-path to point to the
right place (and make sure that that setting precedes the
/usr/local/share/emacs/27.0.50/lisp/org setting that emacs adds):

    (add-to-list 'load-path (expand-file-name "~/elisp/org-mode/lisp"))

Although that has been enough for me, it's probably safer to delete
from load-path all other org entries, thereby making the built-in
version invisible to emacs - in my case, I just have the one:

   (delete "/usr/local/share/emacs/27.0.50/lisp/org" load-path)

That way, if you happen to do something like `(require 'old-org-req)'
with a requirement that is not satisfied by current org, but is
satisfied by the built-in org, you'd get an error, rather than getting
a mixed installation.

> Why does that happen ?
> Can't 9.2.6 override 9.1.9 ? It's not the first time I have issues
> with that situation and that's extremely confusing. What is the best
> way to solve that ?

I think the above should be enough (and IME it is), but maybe someone can
think of other things that might trip one up.


"There are only two hard problems in computer science: cache
invalidation, naming things, and off-by-one errors." -Martin Fowler

  reply	other threads:[~2019-11-26 19:16 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-24 13:37 Jean-Christophe Helary
2019-11-26 19:15 ` Nick Dokos [this message]
2019-11-26 21:41   ` Tim Cross
2019-11-27  2:59     ` Cook, Malcolm
2019-11-27  3:13       ` Jean-Christophe Helary
2019-11-27  6:18         ` Stefan Kangas
2019-11-27 13:23       ` Stefan Monnier
2019-11-27 17:20         ` Cook, Malcolm
2019-11-27 21:51           ` Tim Cross
2019-11-27 22:01           ` Stefan Monnier
2019-11-26 23:14   ` Jean-Christophe Helary
2019-11-27  3:24     ` Stefan Monnier
2019-11-27  5:43       ` Jean-Christophe Helary
2019-11-27  6:00         ` Tim Cross
2019-11-27  6:29           ` Stefan Kangas
2019-11-27  6:42             ` Tim Cross
2019-11-27 10:11               ` Stefan Kangas
2019-11-27 13:21               ` Stefan Monnier
2019-11-27 15:44             ` Eli Zaretskii
2019-11-27  7:04           ` Fraga, Eric
2019-11-27  6:34       ` Stefan Kangas

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:

  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=874kyqcuup.fsf@alphaville.usersys.redhat.com \
    --to=ndokos@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=emacs-orgmode@gnu.org \


* 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


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).