Hi,
Martijn van Duren wrote on Sun, Apr 26, 2020 at 12:52:38PM +0200:
> On 4/26/20 12:27 PM, Thomas de Grivel wrote:
>> Second I don't see this feature described neither in man sh nor man
>> ksh so is it a known behaviour of ksh ?
> from echo(1):
> echo does not support any of the backslash character sequences mandated
> by XSI.
>
> from ksh(1):
> See the print command below for a list of other backslash sequences that
> are recognized.
> ...
> By default, certain C escapes are translated.
So Martijn answered this almost exhaustively.
My only point to add is that i consider it intentional that the
sh(1) manual page does not mention the "echo" builtin because "echo"
cannot be used portably in a /bin/sh program (at least not with
variable expansion following it), and the sh(1) manual starts like
this:
This manual page describes only the parts relevant to a POSIX
compliant sh. If portability is a concern, use only those
features described in this page.
In conclusion, i think there is nothing to fix in the documentation,
neither in echo(1) nor in ksh(1) nor in sh(1).
Yours,
Ingo
No comments:
Post a Comment