zsh-workers
 help / color / mirror / code / Atom feed
From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: Chet Ramey <chet.ramey@case.edu>
Cc: zsh-workers@zsh.org
Subject: Re: PATCH Re: 5.3: printf -
Date: Fri, 16 Dec 2016 00:56:16 +0000	[thread overview]
Message-ID: <20161216005616.GA11824@fujitsu.shahaf.local2> (raw)
In-Reply-To: <e4b5fa2b-2f72-da30-5ec1-6b91e20380e9@case.edu>

Chet Ramey wrote on Thu, Dec 15, 2016 at 18:48:13 -0500:
> On 12/15/16 5:45 PM, Daniel Shahaf wrote:
> 
> > This surprises me; it doesn't match my understanding of the spec.
> > (I thought POSIX would take "--" to be the format string.)
> 
> "Standard utilities that do not accept options, but that do accept
> operands, shall recognize "--" as a first argument to be discarded."
> 
> http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap01.html#tag_17_04

Thank you for the reference.

diff --git a/Test/B03print.ztst b/Test/B03print.ztst
index 7a43f9c..c65568a 100644
--- a/Test/B03print.ztst
+++ b/Test/B03print.ztst
@@ -334,5 +334,3 @@
 0:regression test of printf with assorted ambiguous options or formats
 >------x
 ?(eval):printf:3: not enough arguments
-F:There is some question whether "printf --" should be an error as above,
-F:or should treat "--" as the format string.  Bash agrees on the error.


      reply	other threads:[~2016-12-16  0:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-12 23:41 Daniel Shahaf
2016-12-13  4:21 ` Bart Schaefer
2016-12-13  6:25   ` Daniel Shahaf
2016-12-14  4:48   ` PATCH " Bart Schaefer
2016-12-14  9:39     ` Peter Stephenson
2016-12-14 16:51       ` Daniel Shahaf
2016-12-14 18:44         ` Bart Schaefer
2016-12-15  0:50           ` Daniel Shahaf
2016-12-15  1:14             ` Chet Ramey
2016-12-15 22:45               ` Daniel Shahaf
2016-12-15 23:48                 ` Chet Ramey
2016-12-16  0:56                   ` Daniel Shahaf [this message]

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=20161216005616.GA11824@fujitsu.shahaf.local2 \
    --to=d.s@daniel.shahaf.name \
    --cc=chet.ramey@case.edu \
    --cc=zsh-workers@zsh.org \
    /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).