zsh-workers
 help / color / mirror / code / Atom feed
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 13:51:23 +0100	[thread overview]
Message-ID: <0G0G00B57UDM35@la-la.cambridgesiliconradio.com> (raw)
In-Reply-To: "Your message of Wed, 06 Sep 2000 16:41:15 +0400." <000601c017ff$bedcbad0$21c9ca95@mow.siemens.ru>

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

This is a completely different matter.  The subshell inherits everything
from the parent shell after the fork; it never re-initialiases.  It does
unset the options MONITOR and USEZLE, but not INTERACTIVE, for the
subshell, however.   One might have thought that it would either change all
three or none.  In particular, the effect of claiming to be interactive but
not using ZLE looks a bit weird.  Unless there is some standard behind
this?

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


  parent reply	other threads:[~2000-09-06 12:51 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 [this message]
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=0G0G00B57UDM35@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).