From: Florian Lindner <mailinglists@xgm.de>
To: zsh-users@zsh.org
Subject: Re: Invocation of zshenv
Date: Thu, 17 Jan 2013 10:23:06 +0100 [thread overview]
Message-ID: <36715347.6JBz4RFEZ9@horus> (raw)
In-Reply-To: <20130115130247.6c04e610@pwslap01u.europe.root.pri>
Am Dienstag, 15. Januar 2013, 13:02:47 schrieb Peter Stephenson:
> On Tue, 15 Jan 2013 12:14:45 +0100
>
> Florian Lindner <mailinglists@xgm.de> wrote:
> > I have some PATH, EDITOR and PYTHONPATH set in my .zshenv. As far as
> > I understand it zshenv should be invoced on every kind of shell but
> > when I login using SSH it is not being sourced.
> >
> > What is the file to put such things that should be available in
> > _every_ shell session?
>
> .zshenv is the file to use. If it's not being sourced on some
> occasions, something somewhere is changing the configuration. The only
> ways of doing this I can think of are for something in /etc/zshenv to
> stop it by setting the option NO_RCS, or for the environment variable
> ZDOTDIR to point to a different directory, or for some emulation mode
> such as ksh that doesn't use it to be in effect.
ZDOTDIR and NO_RCS are not set, neither as environment variable nor it's
mentioned in the config.
But actually, I forgot to mention I'm using the grml-zsh-config on Arch.
.zshenv is sourced on normal login shells.
Ivan mentioned a problem regarding /etc/profile. My profile contains:
# Set our default path
PATH="/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin"
export PATH
So it sets and exports the PATH but does not take a already set PATH variable
into account. If .zshenv is sourced before /etc/profile that would explain it.
But why only on SSH shells not on usual shells?
Thanks,
Florian
next prev parent reply other threads:[~2013-01-17 10:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 11:14 Florian Lindner
2013-01-15 13:02 ` Peter Stephenson
2013-01-17 9:23 ` Florian Lindner [this message]
2013-01-17 14:58 ` Bart Schaefer
2013-01-20 18:43 ` Florian Lindner
2013-01-15 13:15 ` Russell Harmon
2013-01-15 15:22 ` Ivan Sichmann Freitas
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=36715347.6JBz4RFEZ9@horus \
--to=mailinglists@xgm.de \
--cc=zsh-users@zsh.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.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).