From: Dave Abrahams <dave@boostpro.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Inferior process mystery
Date: Thu, 26 Apr 2012 12:17:38 -0400 [thread overview]
Message-ID: <m2zk9y31st.fsf@boostpro.com> (raw)
In-Reply-To: <m2mx5zy9jp.fsf@igel.home> (Andreas Schwab's message of "Wed, 25 Apr 2012 20:02:18 +0200")
on Wed Apr 25 2012, Andreas Schwab <schwab-AT-linux-m68k.org> wrote:
> Dave Abrahams <dave@boostpro.com> writes:
>
>> Yep, that is in fact the problem. But how do I discover what is changing my exec-path?
>
> exec-path is initialized from $PATH as inherited by emacs, which appears
> to be different from the one set in your shell.
Yeah, but if I start up with -Q I get something much more reasonable, so
what I need to know is what in my init sequence is munging it.
>> | Original value was
>> | ("/opt/local/bin" "/opt/local/sbin" "/bin" "/sbin" "/usr/bin"
>> | "/usr/sbin"
>> | "/opt/local/var/macports/build/_Users_dave_Public_MacPorts_Portfiles_editors_emacs24-macport/emacs24-macport/work/emacs-24.0.94/lib-src"
>> | "/opt/local/libexec/emacs/24.0.94/x86_64-apple-darwin11.3.0")
>
> This value was set during dumping, and is not very useful as the
> standard value of exec-path.
Actually that would have been a pretty reasonable value. My problem is
that my exec-path is out-of-control, and I don't know why.
--
Dave Abrahams
BoostPro Computing
http://www.boostpro.com
next prev parent reply other threads:[~2012-04-26 16:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-25 14:46 Inferior process mystery Dave Abrahams
2012-04-25 15:21 ` Andreas Schwab
2012-04-25 17:20 ` Dave Abrahams
2012-04-25 18:02 ` Andreas Schwab
2012-04-25 19:15 ` Ivan Andrus
2012-04-26 2:21 ` John Wiegley
2012-04-26 16:17 ` Dave Abrahams [this message]
2012-04-25 15:32 ` Stefan Monnier
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2zk9y31st.fsf@boostpro.com \
--to=dave@boostpro.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=schwab@linux-m68k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs.git
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).