From: Zefram <zefram@fysh.org>
To: Bart Schaefer <schaefer@candle.brasslantern.com>
Cc: zsh-workers@sunsite.dk
Subject: Re: "setopt noexec" and interactive shells
Date: Tue, 27 Mar 2001 19:09:04 +0100 (BST) [thread overview]
Message-ID: <E14hxtw-0005n6-00@crucigera.fysh.org> (raw)
In-Reply-To: <1010325225123.ZM10966@candle.brasslantern.com> from Bart Schaefer at "Mar 25, 2001 10:51:22 pm"
Bart Schaefer wrote:
>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.
By "unsettable" I meant that the shell does not permit one to change
the state of the option. The point is that the shell complains, rather
than giving the superficial appearance of success. Try "set +i" in an
interactive shell for an example of the kind of behaviour I was proposing
for "set -n".
>So the closest thing to "default conditions for interactivity on startup"
>is isatty(0).
By "default conditions ..." I meant also the conditions involving
arguments given to the shell (a shell script normally executes
non-interactively regardless of ttys). All conditions, in fact, other
than shell options (-i). It should also be tested and stored on startup,
where we already have the logic (albeit in a twisted form), rather than
trying to reconstruct it after the fact.
But the ksh semantics aren't very good. I'd be happier with simpler
semantics, that NO_EXEC is ineffective iff INTERACTIVE is on.
I'm basically happy with your patch (or the revised version) in
that it retains the state of NO_EXEC and simply denies it effect,
the way ksh does. I'd still prefer a noisy refusal to set NO_EXEC,
as I proposed above.
>+ if (unset(EXECOPT) && (unset(INTERACTIVE) || !isatty(0)))
As I suggested above, I'd prefer that that condition be
if (unset(EXECOPT) && unset(INTERACTIVE))
-zefram
next prev parent reply other threads:[~2001-03-27 18:09 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
2001-03-25 23:05 ` Bart Schaefer
2001-03-27 18:09 ` Zefram [this message]
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=E14hxtw-0005n6-00@crucigera.fysh.org \
--to=zefram@fysh.org \
--cc=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).