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: Thu, 15 Dec 2016 22:45:12 +0000	[thread overview]
Message-ID: <20161215224512.GA30237@fujitsu.shahaf.local2> (raw)
In-Reply-To: <a582aa63-3f89-6921-564d-61b69efdce20@case.edu>

Chet Ramey wrote on Wed, Dec 14, 2016 at 20:14:31 -0500:
> On 12/14/16 7:50 PM, Daniel Shahaf wrote:
> > Bart Schaefer wrote on Wed, Dec 14, 2016 at 10:44:50 -0800:
> >> On Dec 14,  4:51pm, Daniel Shahaf wrote:
> >> }
> >> } The grandparent patch fixes all the cases given so far in this thread,
> >> } except that "printf --" and "printf -- -" yield an error and "-",
> >> } respectively - whereas in sh mode they should both print "--".
> >>
> >> Bash prints an error and "-" respectively in those two cases as well,
> >> so I think it's unclear what should happen for that in sh mode.
> > 
> > I was aiming for POSIX-compliance, not bash-compliance, for sh mode.
> 
> The format is not optional, according to Posix.

Sure.

> All shells aiming for Posix conformance throw an error on `printf --'.

This surprises me; it doesn't match my understanding of the spec.
(I thought POSIX would take "--" to be the format string.)

Cheers,

Daniel
(trying not to repeat myself _too_ much..)


  reply	other threads:[~2016-12-15 22:48 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 [this message]
2016-12-15 23:48                 ` Chet Ramey
2016-12-16  0:56                   ` Daniel Shahaf

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=20161215224512.GA30237@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).