From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: Re: "setopt noexec" and interactive shells
Date: Sun, 25 Mar 2001 22:51:22 +0000 [thread overview]
Message-ID: <1010325225123.ZM10966@candle.brasslantern.com> (raw)
In-Reply-To: <E14ZkE3-00041Q-00@crucigera.fysh.org>
On Mar 5, 1:55am, Zefram wrote:
} Subject: Re: "setopt noexec" and interactive shells
}
} pdksh 5.2.12 does effectively ignore "set -n" interactively, but [...]
} its condition for overriding is that the shell is interactive and the
} default conditions for interactivity on startup were met -- a shell that's
} explicitly made interactive when it would not otherwise have been does
} honour "set -n" fully.
}
} The other way to do this correctly -- other than ignoring it the way
} pdksh does, that is -- is to make the option unsettable, like -i, under
} the appropriate circumstances. Silent resetting is not good.
There's no way to make the option un-, or rather re-, settable because
once you're not executing commands the state of the shell is effectively
frozen. If ignoreeof is also set, it's painful even to exit.
So the closest thing to "default conditions for interactivity on startup"
is isatty(0). This could of course be fooled by "exec < /dev/tty" or some
such, but if someone is willing to go to that much effort to simulate an
interactive startup ...
Any comments on this patch?
Index: Src/exec.c
===================================================================
--- Src/exec.c 2001/03/24 22:19:24 1.128
+++ Src/exec.c 2001/03/25 22:14:08
@@ -2092,7 +2092,7 @@
zwarn("writing redirection not allowed in restricted mode", NULL, 0);
execerr();
}
- if (unset(EXECOPT))
+ if (unset(EXECOPT) && (unset(INTERACTIVE) || !isatty(0)))
continue;
switch(fn->type) {
case REDIR_HERESTR:
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2001-03-25 22:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-04 5:20 Bart Schaefer
2001-03-05 1:55 ` Zefram
2001-03-25 22:51 ` Bart Schaefer [this message]
2001-03-25 23:05 ` Bart Schaefer
2001-03-27 18:09 ` Zefram
2001-03-27 19:12 ` Zefram
2001-03-30 6:37 ` Bart Schaefer
2001-03-27 19:18 ` Bart Schaefer
2001-03-27 19:25 ` Zefram
2001-03-27 19:58 ` 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=1010325225123.ZM10966@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=zsh-workers@sunsite.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).