ue that POSIX forbids us to support \1 as an extension
> (it says nothing about whether implementations can have additional
> escape sequences). So I'll argue that it is intentional as a dash
> extension. But if you can make dash smaller by getting rid of the
> extension, that might be an
character
>is output.
>
>\\ Output a backslash.
>
>All other backslash sequences elicit undefined behaviour.
>
Then, in the command
echo
because \\ is reached first, then it will be replaced by '\'
character, immediately after that another
sequence.
For instance, the command
echo
prints
\
I think it should print
\\
I don't have to decided how dash should understand things because it
isn't my project. I only advise of a bad behavior, of course from my
point of view.
Bosco.
--
To unsubscribe from this list: send the line
Ahh, now I understood.
In command
echo
first dash interprets the command line (and the arguments), then
internally echo interprets the arguments. But echo is part of dash, so
dash interprets twice the same argument. Sorry I didn't know that.
Thank you for your help and your time.
Bosco
