zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: Re: printf bug(s?)
Date: Fri, 17 Jun 2005 15:47:18 +0000	[thread overview]
Message-ID: <1050617154719.ZM12697@candle.brasslantern.com> (raw)
In-Reply-To: <fb6be96e05061706483b30e32@mail.gmail.com>

On Jun 17,  3:48pm, J wrote:
} Subject: Re: printf bug(s?)
}
} > I may be better off avoiding using \045 anyway and just
} > replace it with %%...
} 
} If I run
} $ printf '\045i' '5+1'
} I would certainly expect it to print 6, and not %i.

Is the printf builtin (or shell utility) specified by POSIX?  If so,
this may be a reasonable question for austin-group interpretation.


  reply	other threads:[~2005-06-17 15:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-17  0:58 Harald van Dijk
2005-06-17  8:15 ` Oliver Kiddle
2005-06-17 13:22   ` Harald van Dijk
2005-06-17 13:48     ` J
2005-06-17 15:47       ` Bart Schaefer [this message]
2005-06-21  9:19         ` Oliver Kiddle

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=1050617154719.ZM12697@candle.brasslantern.com \
    --to=schaefer@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).