Path: csiph.com!news.uzoreto.com!goblin2!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail
From: "Todd A. Jacobs" <tjacobs@codegnome.com>
Newsgroups: gnu.bash.bug
Subject: Re: echo builtin doesn't handle end-of-options flag
Date: Sun, 16 Aug 2020 12:42:31 -0400
Lines: 21
Approved: bug-bash@gnu.org
Message-ID: <mailman.2313.1597596157.2739.bug-bash@gnu.org>
References: <F122E6E9-6067-45EF-8D18-2B1EBF0D5917@codegnome.org> <737d2184-8b59-0eee-4c56-41f7a67d8f88@redhat.com> <9590B2A8-846F-48AB-98AD-E79CFE3C94CF@codegnome.org>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
To: bug-bash@gnu.org
Envelope-to: bug-bash@gnu.org
In-Reply-To: <737d2184-8b59-0eee-4c56-41f7a67d8f88@redhat.com>
Received-SPF: pass client-ip=2607:f8b0:4864:20::72f; envelope-from=tjacobs@codegnome.com; helo=mail-qk1-x72f.google.com
X-Spam_score_int: -18
X-Spam_score: -1.9
X-Spam_bar: -
X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no
X-Spam_action: no action
X-BeenThere: bug-bash@gnu.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Bug reports for the GNU Bourne Again SHell <bug-bash.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/bug-bash>
List-Post: <mailto:bug-bash@gnu.org>
List-Help: <mailto:bug-bash-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=subscribe>
X-Mailman-Original-Message-ID: <9590B2A8-846F-48AB-98AD-E79CFE3C94CF@codegnome.org>
X-Mailman-Original-References: <F122E6E9-6067-45EF-8D18-2B1EBF0D5917@codegnome.org> <737d2184-8b59-0eee-4c56-41f7a67d8f88@redhat.com>
Xref: csiph.com gnu.bash.bug:16761

On Aug 16, 2020, at 12:21 PM, Eric Blake <eblake@redhat.com> wrote:

> I see nothing in your report about bash disobeying POSIX, but rather =
confusion on your part about what POSIX actually requires.

I didn't say it violated POSIX. My expectations were set by the Bash =
Manual, which describes the behavior I'm expecting in the Shell Builtin =
Commands section:

> Unless otherwise noted, each builtin command documented as accepting =
options preceded by =E2=80=98-=E2=80=99 accepts =E2=80=98--=E2=80=99 to =
signify the end of the options.

To be fair, the documentation later calls out that "echo does not =
interpret -- to mean the end of options", but this wasn't obvious on =
first reading. If the demonstrated behavior is correct and/or desirable, =
then it's not a bug. I still found it surprising, but I'm honestly not =
sure how to improve the documentation to draw more attention to the =
known behavior. Maybe it could be bolded, or listed as a caveat, because =
it's easy to overlook.=20=