zsh-users
 help / color / mirror / code / Atom feed
From: "Andrej Borsenkow" <borsenkow.msk@sni.de>
To: "Peter Stephenson" <pws@ibmth.df.unipi.it>,
	"Greg Sylvain" <gsylvain@landmark.com>,
	"Zsh users list" <zsh-users@sunsite.auc.dk>
Subject: RE: Problem w/ ulimit killing compiles on sol 2.4&2.6 ...
Date: Fri, 5 Feb 1999 09:40:28 +0300	[thread overview]
Message-ID: <000501be50d2$6b5b4390$21c9ca95@mowp.siemens.ru> (raw)

>
>   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,

I totally disagree. Anybody doing this will inevitably end up writing
nonportable zsh scripts, that, when used on other system(s), will not work
in the best or will have unpredictable side effects in the worst case.

The only use for zshenv is to setup standard environment (as name suggests).
If you would like to have interactive zsh with specific features - do it in
zshrc. Scripts should _not_ depend on particular option(s) preset or, for
that matter, on particular function(s) being available.

So, I have LD_LIBRARY_PATH in /etc/zshenv, ~/bin in .zshenv - and don't see
much more use for them.

/andrej



             reply	other threads:[~1999-02-05  6:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-05  6:40 Andrej Borsenkow [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-04 13:11 Peter Stephenson
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='000501be50d2$6b5b4390$21c9ca95@mowp.siemens.ru' \
    --to=borsenkow.msk@sni.de \
    --cc=gsylvain@landmark.com \
    --cc=pws@ibmth.df.unipi.it \
    --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).