From: J <jean.chalard@gmail.com>
To: "Harald van Dijk" <truedfx@gentoo.org>
Cc: zsh-workers@sunsite.dk
Subject: Re: printf bug(s?)
Date: Fri, 17 Jun 2005 15:48:30 +0200 [thread overview]
Message-ID: <fb6be96e05061706483b30e32@mail.gmail.com> (raw)
In-Reply-To: <42B2CE98.8070905@gentoo.org>
> Oh, there are other printfs that behave the same? That I didn't know; in
> that case, I may be better off avoiding using \045 anyway and just
> replace it with %%...
My understanding is that for all intents and purposes, printf should
consider a character designed by his octal code as the character
itself, be it a control character or not, pretty much the same way
that the shell interprets it before handing it to the command when
it's enclosed in $'...'. If I run
$ printf '\045i' '5+1'
I would certainly expect it to print 6, and not %i.
Of course that's just what I would expect as a user. Other people may disagree.
--
J
next prev parent reply other threads:[~2005-06-17 13:50 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 [this message]
2005-06-17 15:47 ` Bart Schaefer
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=fb6be96e05061706483b30e32@mail.gmail.com \
--to=jean.chalard@gmail.com \
--cc=truedfx@gentoo.org \
--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).