From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: <zsh-workers@sunsite.auc.dk>
Subject: RE: When should interactive option be set/.zshrc read?
Date: Wed, 6 Sep 2000 17:05:27 +0400 [thread overview]
Message-ID: <000701c01803$20bcb360$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <200009061249.OAA01000@beta.informatik.hu-berlin.de>
> Andrej Borsenkow wrote:
>
> > I was sure, that my .zshrc was read only by interactice zsh, but
> >
> > bor@itsrm2% print $options[interactive]
> > on <= correct
> > bor@itsrm2% : | (print $options[interactive])
> > on <= ?? I doubt, this shell can be considered "interactive"
>
> It's a copy of the interactive shell, a subshell. It doesn't read any
> init files whatsoever.
>
Um, really. Which is even worse.
> Hm, but maybe we should turn off the option in subshells. (And probably
> other options, too?)
>
> Non-interactive shells do things like running shell scripts (`#!.../zsh').
>
By definition, INTERACTIVE is set "if the standard input is a tty and commands
are being read from standard input". In the above case standard input is not
tty and commands are not being read from standard input.
Well, I am concerned now how to prevent all definitions from .zshrc to be used
in subshell. I definitely do not want that (ls foo| ...) use my alias for ls;
and I do not want window title be mangled. Any idea? Is it possible to provide
"clean sandbox" for subshells?
-andrej
next prev parent reply other threads:[~2000-09-06 13:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-06 12:41 Andrej Borsenkow
2000-09-06 12:49 ` Sven Wischnowsky
2000-09-06 13:05 ` Andrej Borsenkow [this message]
2000-09-06 13:12 ` Thomas Köhler
2000-09-06 12:51 ` Peter Stephenson
2000-09-06 13:23 ` Andrej Borsenkow
2000-09-06 14:36 ` Peter Stephenson
2000-09-06 15:25 ` Bart Schaefer
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='000701c01803$20bcb360$21c9ca95@mow.siemens.ru' \
--to=andrej.borsenkow@mow.siemens.ru \
--cc=zsh-workers@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).