zsh-workers
 help / color / mirror / code / Atom feed
From: "Jörg Sommer" <joerg@alea.gnuu.de>
To: zsh-workers@sunsite.dk
Subject: Re: environment settings
Date: Wed, 18 Jun 2008 08:49:03 +0000 (UTC)	[thread overview]
Message-ID: <slrng5hivv.hdr.joerg@alea.gnuu.de> (raw)
In-Reply-To: <20080617093859.GB5016@sc.homeunix.net>

Hi Stephane,

Stephane Chazelas <Stephane_Chazelas@yahoo.fr> wrote:
> On Tue, Jun 17, 2008 at 08:33:02AM +0000, Jörg Sommer wrote:
> [...]
>> > Which in a way makes sense though is not very useful. ~/.zshrc
>> > is your shell configuration file. ~/.zprofile is you session
>> > configuration file.
>> >
>> > Generally, in ~/.zshrc, you put stuff that affects the behavior
>> > of interactive shells (sets shell options, defines shell
>> > aliases, configure completions).
>> >
>> > In ~/.zprofile, you define what affects any process started in
>> > your session not necessarily only the shell processes.
>> 
>> And what's the meaning of .zshenv? I use it for my environment variables
>> like EDITOR, because my session is started by X.
> [...]
>
> Your X login procedure should source your .zprofile

How should this work? How can a binary program or a Perl script source a
shell file?

> .zshenv is to fix up situations where it's not possible in my
> opinion. It's like the SHELLOPTS, BASH_ENV variables with bash
> or ENV with some kshs, it should be used with extreme care and
> probably not permanently.

That .zshenv is evaluated by every script is usable for me, because I set
(or update) the value of http_proxy and ftp_proxy there. Their current
value get's written to a file by a system script and I read these values
in .zshenv.

Bye, Jörg.
-- 
Es liegt in der Natur des Menschen, vernünftig zu denken und
unlogisch zu handeln! Das Gesagte ist nicht das Gemeinte und das Gehörte
nicht das Verstandene!


  parent reply	other threads:[~2008-06-18  8:55 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080616074651.GB26165@marcus>
     [not found] ` <20080616080556.GA5091@sc.homeunix.net>
     [not found]   ` <20080616123045.GC26165@marcus>
     [not found]     ` <20080616124450.GC5091@sc.homeunix.net>
2008-06-17  8:33       ` Jörg Sommer
2008-06-17  9:39         ` Stephane Chazelas
2008-06-17 10:41           ` Vincent Lefevre
2008-06-17 12:58             ` Stephane Chazelas
2008-06-17 13:11               ` Vincent Lefevre
2008-06-17 13:26                 ` Stephane Chazelas
2008-06-17 13:28                   ` Mikael Magnusson
2008-06-17 14:25                     ` Stephane Chazelas
2008-06-17 15:54                       ` Vincent Lefevre
2008-06-17 16:00                         ` Stephane Chazelas
2008-06-17 19:50                           ` Vincent Lefevre
2008-06-17 20:32                             ` Stephane Chazelas
2008-06-18 10:38                               ` Vincent Lefevre
2008-06-18 11:52                                 ` Stephane Chazelas
2008-06-18 17:11                                   ` Bart Schaefer
2008-06-17 14:55                     ` Vincent Lefevre
2008-06-17 14:45                   ` Vincent Lefevre
2008-06-18  8:49           ` Jörg Sommer [this message]
2008-06-18  9:33             ` Stephane Chazelas
2008-06-21  6:26         ` Wayne Davison
2008-06-21 11:36           ` Vincent Lefevre
2008-06-21 12:30             ` Stephane Chazelas
2008-06-22  8:41               ` Vincent Lefevre
2008-06-23 15:24                 ` Stephane Chazelas
2008-06-23 16:16                   ` Vincent Lefevre
2008-06-23 16:20                   ` Bart Schaefer
2008-06-23 16:29                     ` Stephane Chazelas

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=slrng5hivv.hdr.joerg@alea.gnuu.de \
    --to=joerg@alea.gnuu.de \
    --cc=zsh-workers@sunsite.dk \
    /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).