From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: Re: "setopt noexec" and interactive shells
Date: Tue, 27 Mar 2001 19:18:16 +0000 [thread overview]
Message-ID: <1010327191817.ZM14338@candle.brasslantern.com> (raw)
In-Reply-To: <E14hxtw-0005n6-00@crucigera.fysh.org>
On Mar 27, 7:09pm, Zefram wrote:
} Subject: Re: "setopt noexec" and interactive shells
}
} 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.
Aha. But, unlike `interactive', there's no reason not to allow `noexec'
to become set in a shell function, provided that it's going to be restored
again by `localoptions' when the function exits.
That was why my original (some weeks ago) patch reset the option just
before the prompt was printed, rather than disabling it at some lower
level.
} 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.
}
} As I suggested above, I'd prefer that that condition be
}
} if (unset(EXECOPT) && unset(INTERACTIVE))
That's fine with me, too, but I'd still like to hear any thoughts you
have on making `noexec' work within a shell function.
--
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-27 19:18 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
2001-03-27 19:12 ` Zefram
2001-03-30 6:37 ` Bart Schaefer
2001-03-27 19:18 ` Bart Schaefer [this message]
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=1010327191817.ZM14338@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).