GNU bug report logs - #14299
Incorrect output of `printf "\\n"`

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Eric Blake <eblake <at> redhat.com>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#14299: closed (Incorrect output of  `printf "\\n"`)
Date: Mon, 29 Apr 2013 15:43:03 +0000

[Message part 1 (text/plain, inline)]

Your message dated Mon, 29 Apr 2013 09:42:00 -0600
with message-id <517E94C8.5010108 <at> redhat.com>
and subject line Re: bug#14299: Incorrect output of  `printf "\\n"`
has caused the debbugs.gnu.org bug report #14299,
regarding Incorrect output of  `printf "\\n"`
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
14299: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=14299
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Pavel Elkind <elkind <at> chalmers.se>
To: "bug-coreutils <at> gnu.org" <bug-coreutils <at> gnu.org>
Subject: Incorrect output of  `printf "\\n"`
Date: Sun, 28 Apr 2013 18:44:23 +0000

Dear developers,

I found the following potential bug in printf (version 8.17).

Actual result: 
`printf "\\n"` prints a newline caracter.

Expected result:
`printf "\\n"` prints a sequence of two individual characters, '\' and 'n', like '\n',  but  not a newline character.

Please address the above issue,

Many thanks,
Pavel

[Message part 3 (message/rfc822, inline)]

From: Eric Blake <eblake <at> redhat.com>
To: Pavel Elkind <elkind <at> chalmers.se>
Cc: 14299-done <at> debbugs.gnu.org
Subject: Re: bug#14299: Incorrect output of  `printf "\\n"`
Date: Mon, 29 Apr 2013 09:42:00 -0600

[Message part 4 (text/plain, inline)]

tag 14299 notabug
thanks

On 04/28/2013 12:44 PM, Pavel Elkind wrote:
> Dear developers,
> 
> I found the following potential bug in printf (version 8.17).
> 
> Actual result: 
> `printf "\\n"` prints a newline caracter.

Of course.  That's what POSIX requires it to print.

$ set -x
$ printf ".\\n."
+ printf '.\n.'
.
.
$ set -

> 
> Expected result:
> `printf "\\n"` prints a sequence of two individual characters, '\' and 'n', like '\n',  but  not a newline character.

If you want printf to print a literal backslash, you have to properly
escape it.  There are two levels of escaping to consider; shell escaping
(before printf ever sees its argv), and printf escaping.  You missed a
level, because you forgot that within "", the shell converts \\ into a
literal \ as part of the argv, and as my 'set -x' trace showed above,
you were passing only one backslash, not two, to printf.  Within printf,
when it sees the single backslash-n sequence, it converts that escape
sequence to newline.

You probably meant to do any one of these equivalent actions:

printf '.\\n.'
printf .\\\\n.
printf ".\\\\n."

all of which result in the argv handed to printf still containing two
backslashes.

As such, I'm closing this as not a bug, although you may continue to
reply here if you have further comments.

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org

[signature.asc (application/pgp-signature, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.