On 2013-01-29 14:31, Gary V. Vaughan wrote: > Hi Peter, > > On 29 Jan 2013, at 20:17, Peter Rosin <[email protected]> wrote: >> On 2013-01-29 13:27, Gary V. Vaughan wrote: >>> >>> Normally, @command{printf} is safer and easier to use than @command{echo} >>> -and @command{echo -n}. Thus, you should use @command{printf '%s\n'} >>> +and @command{echo -n}. Thus, you should use @command{printf "%s\n"} >> >> Shouldn't it be >> >> printf "%s\\n" >> >> when you write it outside single quotes? > > Apparently not; before my original patch, AS_ECHO would (under the right > circumstances) expand to 'printf "%s\n"' (single backslash), and indeed > passes the testsuite again now that I've patched it to expand to the same > under all circumstances.
Right, to the shell "\n" is the same as "\\n", I see that now. It just felt wrong to not escape the escape character. Sorry for the noise. Cheers, Peter
