From: Denys Vlasenko <vda.linux@googlemail.com>
To: Herbert Xu <herbert@gondor.apana.org.au>,
DASH shell mailing list <dash@vger.kernel.org>
Subject: set -I is not required by standard, and does not match bash
Date: Mon, 4 Jan 2021 13:22:30 +0100 [thread overview]
Message-ID: <CAK1hOcPjYpXa8GQsD5dmYnkUHqc_KC2BXj0NC6d49qi10Qt4kA@mail.gmail.com> (raw)
Hello,
In dash, set -I is a short-option alias to set -o ignoreeof.
However, bash does not have such alias, it has an undocumented
set -I which switches off "invisible variables"
(I don't know what that is).
Standards do not mention any -I option.
I propose, in the interests of keeping things less disparate,
to remove set -I support from dash: make "ignoreeof" to be
only an -o long option.
next reply other threads:[~2021-01-04 12:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 12:22 Denys Vlasenko [this message]
2021-01-04 12:49 ` set -I is not required by standard, and does not match bash Herbert Xu
2021-01-04 21:19 ` Harald van Dijk
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=CAK1hOcPjYpXa8GQsD5dmYnkUHqc_KC2BXj0NC6d49qi10Qt4kA@mail.gmail.com \
--to=vda.linux@googlemail.com \
--cc=dash@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
/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.
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).