I'm using bash :)
**printenv
...
SHELL=/bin/bash
...
Although 'which echo' reports /bin/echo, echo has an unlogical behavior:
echo -E "foo\n"
-E foo
/bin/echo -E "foo\n"
foo\n
(This was done within a Makefile. Doing this in my shell outputs the
same thing as /bin/echo in a Makefile, which is logical since they
should be the same command.)
Regards,
Vincent Tabard
Radio Pytagor : http://www.radiopytagor.com/
Julien Cristau a écrit :
On Tue, Jun 5, 2007 at 22:32:06 +0200, Vincent Tabard wrote:
Yup... "echo" fails for me... it converts by default all the "escape
strings" (\t, \n, etc) that are present in the strings (\title,
\newpage). It is *not* the default behavior of /bin/echo on my system
(GNU), and the -E option does not work, so I guess some "builtin" kind
of echo must come in the way.
gah, looks like zsh's (i guess that's what you're using?) echo
interprets escape sequences by default. sigh. that said, the makefiles
should use /bin/sh, not zsh (and having /bin/sh symlinked from zsh is
wrong, IMO).
maybe like this:
printf "%s\n" "\foo\bar"
?
Cheers,
Julien
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Savonet-devl mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/savonet-devl
