Eric Blake a écrit :
That's bash's rules. According to POSIX, "\n" has undefined behavior. And in some other implementations, such as Solaris sh, "\n" is interpolated by the shell as a newline. Bash instead does the interpolation when you use $'\n'.
isn't it the echo command which interpret the \n sequence ? could you try using : printf ":%s:\n" "x\nx"
But the moral of the story is that within "", it is only portable to use \ if it is followed by one of the four bytes specifically documented by POSIX.
whatever the shell I've tested, the answer was : :x\nx: even on solaris 9 using /sbin/sh or hp-ux 11i using /usr/old/bin/sh Regards, Cyrille Lefevre -- mailto:cyrille.lefevre-li...@laposte.net -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
