unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Robert Thorpe <rt@robertthorpeconsulting.com>
To: Emanuel Berg <moasen@zoho.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: emacs doesn't inherit PATH from environment
Date: Wed, 14 Feb 2018 01:32:52 +0000	[thread overview]
Message-ID: <87zi4cs6d7.fsf@robertthorpeconsulting.com> (raw)
In-Reply-To: <864lmkhff0.fsf@zoho.com> (message from Emanuel Berg on Tue, 13 Feb 2018 20:12:51 +0100)

Emanuel Berg <moasen@zoho.com> writes:

> Shell stuff that I want available from Emacs
> I have to set in a special file for zsh, which
> is
>
>     ~/.zshenv
>
> If I put the same thing in plain .zshrc or
> a file loaded from there, it doesn't work!
>
> I never understood why because the Emacs
> instance is run from a zsh shell, but for some
> reason Emacs cannot see zsh stuff that aren't
> defined in that special file, even when (as
> said) executed from a point which HAS access to
> it all!

I suspect that this is due to the differences between various shells.
There are login shells and non login shells.  There are interactive
shells and non-interactive shells.  These behave in different ways.
They load different variables and they reveal different things to other
programs and shells executed within them.

Using shells from within Emacs can cause problems with these defaults
because it can trick the shell into thinking that the use is
non-interactive.

Have a look at th Zsh documentation, it will probably explain some
obscure caveats about using .zshrc.

BR,
Robert Thorpe



  parent reply	other threads:[~2018-02-14  1:32 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.8985.1518453550.27995.help-gnu-emacs@gnu.org>
2018-02-13 19:12 ` emacs doesn't inherit PATH from environment Emanuel Berg
2018-02-13 23:57   ` Larry Evans
     [not found]   ` <mailman.9069.1518566292.27995.help-gnu-emacs@gnu.org>
2018-02-14  0:11     ` Emanuel Berg
2018-02-14  0:48       ` Larry Evans
2018-02-14  1:45         ` Robert Thorpe
2018-02-14  2:35           ` Larry Evans
     [not found]       ` <mailman.9071.1518569365.27995.help-gnu-emacs@gnu.org>
2018-02-14  1:23         ` Emanuel Berg
2018-02-14  1:25         ` Emanuel Berg
2018-02-14  1:32   ` Robert Thorpe [this message]
2018-02-14 19:19   ` Bastian Beischer
     [not found]   ` <mailman.9115.1518635972.27995.help-gnu-emacs@gnu.org>
2018-02-16 17:14     ` Emanuel Berg
     [not found] <mailman.9076.1518571984.27995.help-gnu-emacs@gnu.org>
2018-02-14  1:43 ` Emanuel Berg
2018-02-12 15:51 Larry Evans
2018-02-14  1:27 ` Glenn Morris
2018-02-14  2:24   ` Larry Evans
2018-02-14 14:53     ` Larry Evans
2018-02-14 23:18       ` Robert Thorpe
2018-02-15  1:03         ` Larry Evans
2018-02-15  2:38           ` Bob Proulx
     [not found]           ` <mailman.9140.1518662330.27995.help-gnu-emacs@gnu.org>
2018-02-15 15:59             ` Barry Fishman
2018-02-15 20:18               ` Bob Proulx
     [not found]         ` <mailman.9127.1518652911.27995.help-gnu-emacs@gnu.org>
2018-02-16 16:58           ` Emanuel Berg
     [not found]     ` <mailman.9096.1518616283.27995.help-gnu-emacs@gnu.org>
2018-02-16 16:54       ` Emanuel Berg
     [not found] ` <mailman.9075.1518571658.27995.help-gnu-emacs@gnu.org>
2018-02-14  1:38   ` Emanuel Berg

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=87zi4cs6d7.fsf@robertthorpeconsulting.com \
    --to=rt@robertthorpeconsulting.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=moasen@zoho.com \
    /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.
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).