From: email@example.com (Thomas S. Dye)
Cc: Org-mode <firstname.lastname@example.org>
Subject: Re: list-load-path-shadows
Date: Wed, 05 Sep 2012 09:40:16 -1000 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <firstname.lastname@example.org> (Nick Dokos's message of "Wed, 05 Sep 2012 15:20:33 -0400")
Nick Dokos <email@example.com> writes:
> Thomas S. Dye <firstname.lastname@example.org> wrote:
>> Hmm, after putting your minimal .emacs (suitably localized) in ~/temp,
>> emacs -Q -l /Users/dk/temp/.emacs launches emacs and opens the minimal
>> .emacs file for editing, but apparently doesn't source it. M-x
>> locate-library RET org RET points to the org that ships with my emacs,
>> rather than to the one indicated in the minimal .emacs.
>> Following some advice on EmacsWiki, I have this in .bashrc:
>> alias emacs='/Applications/Emacs.app/Contents/MacOS/Emacs'
>> alias emacsclient='/Applications/Emacs.app/Contents/MacOS/bin/emacsclient'
> What happens if you bypass the alias?
> /Applications/Emacs.app/Contents/MacOS/Emacs -Q -l /Users/dk/temp/.emacs
> If it still doesn't work, I'll give up: MacOS emacs seems to be a very
> different beast from any emacs I know.
Apparently a very different beast :(
Thanks for your help. I probably wouldn't have thought to wonder
whether my emacs was the culprit. I guess I'll try a different
installation to see what shakes out.
All the best,
Thomas S. Dye
next prev parent reply other threads:[~2012-09-05 19:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-04 16:33 list-load-path-shadows Thomas S. Dye
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 ` Thomas S. Dye [this message]
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).