Mike Frysinger 670c3f7822 echo: make escape sequences depend on fancy mode ...

Currently when you disable fancy echo, escape sequences are hardcoded
enabled (e.g. as if you used `echo -e` all the time).  The opposite
behavior is more desirable (always disable -e support) because:
* This seems to contradict the spirit of the kconfig help text (where
  it says enable support for -n/-e flags), although you could say that
  we aren't supporting the -e flag directly as `echo -e` will show the
  -e flag.
* POSIX makes escape sequences optional, and even says they are there
  only on XSI-conformant systems.
* It saves space (~100 bytes on x86_64).
* It makes things faster!
* It makes it behave more like bash where you need an explicit -e flag
  in order for escape sequences to be interpreted.

Signed-off-by: Mike Frysinger <vapier@gentoo.org>
Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>

2015-07-31 03:47:49 +02:00

..

libcoreutils

…

basename.c

…

cal.c

…

cat.c

…

catv.c

…

chgrp.c

…

chmod.c

…

chown.c

…

chroot.c

…

cksum.c

…

comm.c

…

Config.src

…

cp.c

…

cut.c

…

date.c

…

dd.c

…

df.c

…

dirname.c

…

dos2unix.c

…

du.c

…

echo.c

echo: make escape sequences depend on fancy mode

2015-07-31 03:47:49 +02:00

env.c

…

expand.c

…

expr.c

…

false.c

…

fold.c

…

fsync.c

…

head.c

…

hostid.c

…

id_test.sh

…

id.c

…

install.c

…

Kbuild.src

…

length.c.disabled

…

ln.c

…

logname.c

…

ls.c

…

md5_sha1_sum.c

…

mkdir.c

…

mkfifo.c

…

mknod.c

…

mv.c

…

nice.c

…

nohup.c

…

od_bloaty.c

…

od.c

…

printenv.c

…

printf.c

…

pwd.c

…

readlink.c

…

realpath.c

…

rm.c

…

rmdir.c

…

seq.c

…

shuf.c

…

sleep.c

…

sort.c

…

split.c

…

stat.c

…

stty.c

…

sum.c

…

sync.c

…

tac.c

…

tail.c

…

tee.c

…

test_ptr_hack.c

…

test.c

…

touch.c

…

tr.c

…

true.c

…

truncate.c

…

tty.c

…

uname.c

…

uniq.c

…

unlink.c

…

usleep.c

…

uudecode.c

…

uuencode.c

…

wc.c

…

who.c

…

whoami.c

…

yes.c

…