emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: makefile for v. 7.9.1 on Windows 7 doesn't work
Date: Mon, 10 Sep 2012 21:24:52 +0200	[thread overview]
Message-ID: <87ipblisu3.fsf@Rainer.invalid> (raw)
In-Reply-To: CA+M2ft8+uW6k5k6AUYr-AsYMx+NOCNY8t1YNvQLeetPapCFRKQ@mail.gmail.com

John Hendy writes:
>> I don't really know where your other problems come from, but it seems
>> that whatever you are invoking as "emacs" fails to properly set up the
>> load path.  You can try and replace the "-L" option with "--directory".
> I'll definitely try this. Where should the load path point? My emacs
> dir, or the org git dir?

What I meant was that if you add something to load-path via this option,
make sure it actually turns up _first_ in the load-path.  Like

emacs -L blafasel

should then have "blafasel" as the first component in load-path.  If
emacs is invoked via a wrapper scriptit may inject other options in
places that subvert this.  Another possibility is that an environment
variable EMACS_LOADPATH is set (or gets set by some wrapper) when emacs
is started, this would also explain why the load-path doesn't end up
what it's supposed to be.

+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf rackAttack V1.04R1:

  reply	other threads:[~2012-09-10 19:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-07  7:13 makefile for v. 7.9.1 on Windows 7 doesn't work Bostjan Vilfan
2012-09-07 12:33 ` John Hendy
2012-09-07 12:45   ` Jonathan Leech-Pepin
2012-09-07 13:05     ` John Hendy
2012-09-07 13:14       ` Bastien
2012-09-07 13:27         ` John Hendy
2012-09-07 13:32       ` Jonathan Leech-Pepin
2012-09-07 19:00   ` Achim Gratz
2012-09-10 17:59     ` John Hendy
2012-09-10 19:24       ` Achim Gratz [this message]
2012-09-10 19:48         ` John Hendy
2012-09-10 19:58           ` Achim Gratz
2012-09-10 20:01           ` Nick Dokos
2012-09-07 16:42 Bostjan Vilfan
2012-09-08  6:56 ` Bastien

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=87ipblisu3.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --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).