From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.auc.dk (Zsh hackers list)
Subject: Re: When should interactive option be set/.zshrc read?
Date: Wed, 06 Sep 2000 15:36:22 +0100 [thread overview]
Message-ID: <0G0G00BNXZ8L35@la-la.cambridgesiliconradio.com> (raw)
In-Reply-To: "Your message of Wed, 06 Sep 2000 17:23:49 +0400." <000801c01805$b10d35f0$21c9ca95@mow.siemens.ru>
Andrej wrote:
> "Environment" includes current option settings, aliases, functions
> etc. SUS V2 shell supports job control, and has MONITOR option that is on
> if shell is interactive. But it is silent on what happens with these
> options in subshell.
This probably means we've already broken it by unsetting MONITOR, in which
case unsetting INTERACTIVE as well would be logical.
However, it's not true that running in a subshell changes the basic feature
of an interactive shell: standard input remains the tty, and the shell
continues to read commands from the usual source --- unless, of course, the
subshell is for some special purpose, such as a command substitution or
part of a pipeline. But by that score we would have to unset INTERACTIVE
when the current shell is running as the righthand side of a pipeline,
which is clearly not on. So it's not all that clear cut.
--
Peter Stephenson <pws@csr.com> Software Engineer
Cambridge Silicon Radio, Unit 300, Science Park, Milton Road,
Cambridge, CB4 0XL, UK Tel: +44 (0)1223 392070
next prev parent reply other threads:[~2000-09-06 14:37 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
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 [this message]
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=0G0G00BNXZ8L35@la-la.cambridgesiliconradio.com \
--to=pws@csr.com \
--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).