Thanks you all,
Again I see that this printf we can use. But there are some scenarios where
the o/p does not exactly match with echo. So still its good to have a way
to pirnt -n /-e/-E with echo. Can this be considered as bug and can this be
fixed?
Thanks & Regards
--Jyoti
****************************************
Jyoti Tenginakai
AIX-Security Development Team
IBM India Software Lab
EGD 'D' Block Sixth Floor
Off Indiranagar Koramangala Intermediate Ring Road
Bangaluru - 560071
ph: 41776666
extn: 76666
Mail:jyoti....@in.ibm.com
From: Chet Ramey <chet.ra...@case.edu>
To: Jyoti B Tenginakai <jyoti....@in.ibm.com>, Pierre Gaston
<pierre.gas...@gmail.com>
Cc: chet.ra...@case.edu, Sangamesh Mallayya
<sangamesh.sw...@in.ibm.com>, "bug-bash@gnu.org"
<bug-bash@gnu.org>
Date: 02/02/2017 11:21 PM
Subject: Re: echo -n
On 2/2/17 11:56 AM, Jyoti B Tenginakai wrote:
> HI All,
>
> Thanks for your quick response.
>
> I have tried using the printf instead of echo. But the issue with printf
is
> , the behaviour is not consistent with what echo prints for all the
inputs
> i.e.
> In my script I am generically using echo for all the options. If I have
to
> use printf instead of it should behave consistently .
> if echo * is passed to bash shell, the o/p shows the \t seperated values
> whereas with printf '%s' *, it won't display space separated output.
Again
> printf '%s ' # behaviour is different from what echo # shows
echo()
{
builtin printf "%s\n" "$*"
}
You can make this more elaborate if you want.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU c...@case.edu
http://cnswww.cns.cwru.edu/~chet/
