From: Peter Stephenson <pws@ibmth.df.unipi.it>
To: "Greg Sylvain" <gsylvain@landmark.com>,
zsh-users@sunsite.auc.dk (Zsh users list)
Subject: Re: Problem w/ ulimit killing compiles on sol 2.4&2.6 ...
Date: Thu, 04 Feb 1999 14:11:20 +0100 [thread overview]
Message-ID: <9902041311.AA56293@ibmth.df.unipi.it> (raw)
I've just put this together.
3.2: In which startup file do I put...?
When zsh starts up, there are four files you can change which it will
run under various circumstances: .zshenv, .zprofile, .zshrc
and .zlogin. They are usually in your home directory, but the
variable $ZDOTDIR may be set to alter that. Here are a few simple
hints about how to use them. There are also files which the system
administrator can set for all shells; you can avoid running all except
/etc/zshenv by starting zsh with the -f option --- for this
reason it is important for administrators to make sure /etc/zshenv
is as brief as possible.
The order in which the four files are searched (none of them _need_
to exist) is the one just given. However, .zprofile and .zlogin
are only run when the shell is a login shell --- when you first login,
of course, and whenever you start zsh with the -l option. All
login shells are interactive. The order is the only difference
between those; you should decide whether you need things set before or
after .zshrc. These files are a good place to set environment
variables (i.e. `export' commands), since they are passed on to
all shells without you having to set them again, and also to check
that your terminal is set up properly (except that if you want to
change settings for terminal emulator windows like xterm you will
need to put those in .zshrc, since usually you do not get a login
shell here).
The only file you can alter which is started with every zsh (unless
you use the -f option) is .zshenv, so this is a good place to
put things you want even if the shell is non-interactive: options for
changing the the syntax, like EXTENDED_GLOB, any changes to set with
`limit', any more variables you want to make sure are set as for
example $fpath to find functions. You almost certainly do not
want .zshenv to produce any output.
Finally, .zshrc is run for every interactive shell; that includes
login shells, but also any other time you start up a shell, such as
simply by typing `zsh' or opening a new terminal emulator window.
This file is the place to change the editing behaviour via options or
`bindkey', control how your history is saved, set aliases unless
you want to use them in scripts too, and for any other clutter which
can't be exported but you only use when interacting directly with the
shell. You probably don't want .zshrc to produce output, either,
since there are occasions when this can be a problem, such as when
using `rsh' from another host. See 3.21 for what to
put in .zshrc to save your history.
--
Peter Stephenson <pws@ibmth.df.unipi.it> Tel: +39 050 844536
WWW: http://www.ifh.de/~pws/
Dipartimento di Fisica, Via Buonarroti 2, 56127 Pisa, Italy
next reply other threads:[~1999-02-04 13:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-04 13:11 Peter Stephenson [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-02-05 9:02 Peter Stephenson
1999-02-05 8:28 Bart Schaefer
1999-02-05 6:40 Andrej Borsenkow
1999-02-04 8:46 Peter Stephenson
1999-02-03 19:23 Bart Schaefer
1999-02-03 18:48 Sweth Chandramouli
1999-02-03 18:29 Greg Sylvain
1999-02-03 18:09 Greg Sylvain
1999-02-03 17:54 Bart Schaefer
1999-02-03 17:38 Greg Sylvain
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=9902041311.AA56293@ibmth.df.unipi.it \
--to=pws@ibmth.df.unipi.it \
--cc=gsylvain@landmark.com \
--cc=zsh-users@sunsite.auc.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).