emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Hendy <jw.hendy@gmail.com>
To: Suvayu Ali <fatkasuvayu+linux@gmail.com>
Cc: adam <ahcnz@orcon.net.nz>, emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: mixed orgmode installation
Date: Sun, 8 Sep 2013 10:26:01 -0500	[thread overview]
Message-ID: <CA+M2ft909emeFpWGyAeG8gTokUAQ5zwppqyKhfzXaUNHb9Fe=w@mail.gmail.com> (raw)
In-Reply-To: <20130908151042.GH20690@kuru.dyndns-at-home.com>

On Sun, Sep 8, 2013 at 10:10 AM, Suvayu Ali <fatkasuvayu+linux@gmail.com> wrote:
> On Sun, Sep 08, 2013 at 09:37:23AM -0500, John Hendy wrote:
>> On that note, is there a recommended "diagnosis" route someone could
>> recommend other than simply `M-x org-version`? Is it possible to get,
>> e.g. 8.0.7, from that command but be pulling from mixed org locations
>> (org shipped with Emacs, and org from tgz or git)? If so, I was
>> unaware, so it'd be great to understand how one can do a full
>> diagnostic.
> When in doubt, Worg is always your friend ;):
>   <http://orgmode.org/worg/org-faq.html#mixed-install>

I take it I'm a bad friend, as I apparently forget about that one
constantly with this list :)

So... from that page, here are my tools:
- `M-x org-version` : if that lists what you think it should via your
git or snapshot... so far so good

- If `M-x list-load-path-shadows` looks like...???... then you're
good. I'm assuming it should look like this:

#+begin_src list-load-path-shadows

~/.elisp/org.git/lisp/ob-latex hides /usr/share/emacs/24.3/lisp/org/ob-latex
~/.elisp/org.git/lisp/ob-scala hides /usr/share/emacs/24.3/lisp/org/ob-scala
~/.elisp/org.git/lisp/org-src hides /usr/share/emacs/24.3/lisp/org/org-src
~/.elisp/org.git/lisp/ob-java hides /usr/share/emacs/24.3/lisp/org/ob-java


94 Emacs Lisp load-path shadowings were found


I'm not sure how many there should be, but they all come from from my
git repo and shadow something in my emacs installation. That still
leaves two possibly redundant questions:

- How do I find out what's *not* shadowed?
- How do I find out how many Lisp load-path shadowings there *should
be* with a correct, non-mixed installation?

Then again, is Worg saying that if `M-x org-version` outputs the
"correct" answer... we're all set and there's nothing to worry about?
In other words, it won't output the correct, git-pointing,
version/path unless *everything* provided by the built-in Org has been
replaced by the snapshot/git version?


> --
> Suvayu
> Open source is the future. It sets us free.

  reply	other threads:[~2013-09-08 15:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-04 13:52 mixed orgmode installation Johannes Rainer
2013-09-04 14:19 ` Thorsten Jolitz
2013-09-04 14:52   ` Johannes Rainer
2013-09-04 15:07     ` Suvayu Ali
2013-09-08  5:40       ` adam
2013-09-08 14:37         ` John Hendy
2013-09-08 15:10           ` Suvayu Ali
2013-09-08 15:26             ` John Hendy [this message]
2013-09-08 16:52               ` Achim Gratz
2014-01-02  8:06                 ` Justin Gordon
2014-01-03  8:43                   ` Sharon Kimble
2014-01-03 18:08                     ` Justin Gordon
2014-01-03 18:49                   ` John Hendy
2013-09-04 19:20 ` Achim Gratz
2013-09-08 14:31   ` John Hendy
2013-09-08 16:41     ` Achim Gratz
2013-09-08 17:52       ` John Hendy
2013-09-08 18:39         ` Achim Gratz

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='CA+M2ft909emeFpWGyAeG8gTokUAQ5zwppqyKhfzXaUNHb9Fe=w@mail.gmail.com' \
    --to=jw.hendy@gmail.com \
    --cc=ahcnz@orcon.net.nz \
    --cc=emacs-orgmode@gnu.org \
    --cc=fatkasuvayu+linux@gmail.com \


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