Re: Why doesn't compile command set path from login shell

>>>>> "Larry" == Larry Evans <[email protected]> writes:

    Larry>  From Xemacs, when the `Shell command` from tools menu is
    Larry> used, the path is not what's produced by my login shell
    Larry> script, .bash_profile.  OTOH, when the `Shell` command from
    Larry> the tools menu is invoked, I get an e-shell in which:

bash has a ridiculously hairy startup process; this probably has
something to do with that.  What's an "e-shell"?  Do you mean the
eshell package which implements a shell in elisp?

AFAIK XEmacs itself does not set environment variables at all.  If
you invoke XEmacs from a login shell, it will inherit the PATH from
its environment, and pass that in the environment of both interactive
and batch shells under it.  XEmacs should not be creating login shells
as subprocesses, so the profile will not be sourced.

If that's not what you're getting, then your may have something set in
the BASH_ENV or ENV environment variables, or in your .bashrc, which
can cause a difference since batch shells read the former while
interactive shells read the latter.  Or the shell may be being invoked
as "sh", in which case it ignores all the bash-specific files.  Check
to see what the value of `shell-file-name' is, and the SHELL
environment variable when XEmacs is invoked.

Finally, the `setenv' command may be used in a package or in your
startup files to set environment variables like PATH.  I don't know of
any XEmacs packages that would set PATH, though.

-- 
School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba                    Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
               Ask not how you can "do" free software business;
              ask what your business can "do for" free software.