From: firstname.lastname@example.org (Thomas S. Dye)
To: Org-mode <email@example.com>
Date: Tue, 04 Sep 2012 06:33:42 -1000 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
I'm working to understand why my initialization files don't work if I
compile org from git, but do seem to work (that is, initialization runs
to completion) when I don't compile org from git. Right now I've
installed org from git and have run make uncompiled.
Because mixed installations are common, I'm following the FAQ "Is my
Orgmode installation mixed?"
(org-version) looks good:
Org-mode version 7.9.1 (release_7.9.1-138-geeb5b9 @
The FAQ advises that I go through the output of list-load-path-shadows
line by line to get hints, but fails to mention what might qualify as a
hint. So, I'm coming to the list to check if any of the shadow patterns
I'm seeing might be hints.
I see that 110 Emacs Lisp load-path shadowings were found.
108 of the shadowings are cases where a file in
~/.emacs.d/src/org-mode/lisp (my home for the git version of org mode)
hides a file of the same name in
/Applications/Emacs.app/Contents/Resources/lisp/org/. I think these 108
shadowings are the right thing, and that they are not hints that
something is wrong. Is 108 shadowings the correct number for a normal
org mode installation nowadays?
The other two are different.
The first one is:
Here, the file created by the emacs Customize interface is on the
load-path and shadows something completely different (and important?),
though not part of org mode. Should I do something to have the emacs
Customize interface put the file somewhere off the load-path?
The second one is:
I keep hoping gnus will heal itself and stop hanging emacs--could this
shadowing be causing problems?
All the best,
Thomas S. Dye
next reply other threads:[~2012-09-04 16:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-04 16:33 Thomas S. Dye [this message]
2012-09-04 17:34 ` list-load-path-shadows Nick Dokos
2012-09-05 3:16 ` list-load-path-shadows Thomas S. Dye
2012-09-05 13:54 ` list-load-path-shadows Nick Dokos
2012-09-05 16:57 ` list-load-path-shadows Thomas S. Dye
2012-09-05 18:00 ` list-load-path-shadows Nick Dokos
2012-09-05 18:51 ` list-load-path-shadows Thomas S. Dye
2012-09-05 19:20 ` list-load-path-shadows Nick Dokos
2012-09-05 19:40 ` list-load-path-shadows Thomas S. Dye
2012-09-05 20:01 ` list-load-path-shadows Nick Dokos
2012-09-05 20:58 ` list-load-path-shadows Thomas S. Dye
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 \
* 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).