Zsh Mailing List Archive
Messages sorted by:
Re: using variables from .zshenv in shell scripts
- X-seq: zsh-users 19555
- From: TJ Luoma <luomat@xxxxxxxxx>
- To: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- Subject: Re: using variables from .zshenv in shell scripts
- Date: Wed, 17 Dec 2014 14:08:45 -0500
- Cc: Zsh-Users List <zsh-users@xxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=R14YJYCbdPrPUTbb43m76yA2iBQRqYfVUF9dqKUVjK0=; b=x7ItRjOy7iBzMBjNv4lKH42KzB0lSpCHoCDqd5WuPSleECBpuLNYAbJ8l552+RMdZa 6thuHYQBHkxa08FBPUwQITMlDfwAyBQuDA5wO/vhABrLJYbnad6M1p9emeWIRJ+YGhm7 G6cgt7OjvIotYaQ4+aoH4n1biHjeHZmuhhi4ZGJyqEuSebsew3xWgIXHL3rWWwbKkgnS lZSRWf3IA7iRuy+xtQth5spIziJb8nSxyi4mIAZRLIt4RKv783SWMWAKU03HiLTC4+EZ YEVwFAKJnjauoPLc52iokNN49JHIiuMFgkBCoORd45fUq4NIDhUhlJfOvCgRDI59nker 9JCQ==
- In-reply-to: <141217090406.ZM583@torch.brasslantern.com>
- List-help: <mailto:firstname.lastname@example.org>
- List-id: Zsh Users List <zsh-users.zsh.org>
- List-post: <mailto:email@example.com>
- Mailing-list: contact zsh-users-help@xxxxxxx; run by ezmlm
- References: <CADjGqHsNGPo5ikqitcpGq49ZpTAJKvoNHmMW-sW6epR5m6+cyQ@mail.gmail.com> <141217090406.ZM583@torch.brasslantern.com>
Now it's doing it, when it wasn't before.
I am left to assume that I had somehow managed to not actually save
the changes to my ~/.zshenv or some such oddity, because I cannot
duplicate it now.
All I need is 3-4 weeks of sleep and I'm sure I'll be back on top of things.
Sorry for the bother
On Wed, Dec 17, 2014 at 12:04 PM, Bart Schaefer
> On Dec 17, 11:16am, TJ Luoma wrote:
> } I have some variables set in ~/.zshenv which I want to use in shell
> } scripts
> } However, those variables do not seem to be defined when the shell
> } script runs.
> Is there possibly a value for ZDOTDIR already in your environment when
> the script runs?
> It's also possible that /etc/zshenv is doing something that causes your
> $HOME/.zshenv to be skipped.
> Try using
> #!/bin/zsh -x
> in the script to see what's actually executing.
Messages sorted by: