Avoid using `echo' in ksh #2

clarkwang opened this Issue Mar 27, 2012 · 1 comment


None yet
2 participants

The echo command is not portable. For example, ksh's echo does not support -n option and it interpretes \b as the special char BACKSPACE.

lib/msg.sh:_Dbg_msg_nocr(): echo -n ==> This causes test/unit/test-fns.sh:test_fns_msg() to fail.

rocky added a commit that referenced this issue Mar 27, 2012


rocky commented Mar 27, 2012

Commit b280a71 replaces echo -n with printf "%s". See if that works, and if so, close this issue. Thanks.

@clarkwang clarkwang closed this Mar 28, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment