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: Mon, 5 Mar 2001 01:55:51 +0000 (GMT) [thread overview]
Message-ID: <E14ZkE3-00041Q-00@crucigera.fysh.org> (raw)
In-Reply-To: <1010304052058.ZM13951@candle.brasslantern.com> from Bart Schaefer at "Mar 4, 2001 05:20:57 am"
Bart Schaefer wrote:
>I've noticed that bash won't honor "set -n" when the shell is interactive;
>but zsh will happily do so, leaving you with a useless prompt.
Experimentally, bash 2.04.12 does honour "set -n" fully.
>Perhaps a happy compromise would be to force "setopt exec" just before
>executing precmd? Any reason to test e.g. `!justonce' before doing this?
I just think it's a bad idea. "set -n" has perfectly well-defined
semantics, and we shouldn't ignore those semantics just because it's
probably not what the user wanted. "set -n" is not fundamentally
incompatible with interactivity.
>Having just typo'd "set -n ..." for "sed -n ...",
Tee hee. Of course, you could equally well have typoed "kill -9 $$"
for "kill -9 $!".
>+ opts[EXECOPT] = 1;
And if you're going to ignore "set -n", this is the wrong way to do it.
pdksh 5.2.12 does effectively ignore "set -n" interactively, but it
does this by allowing the option to be set (such that "n" appeans in
$-) but then ignoring the option's state if interactive. Actually,
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.
-zefram
next prev parent reply other threads:[~2001-03-05 1:56 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 [this message]
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
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=E14ZkE3-00041Q-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).