On 9/2/15 5:10 PM, Helmut Karlowski wrote:
>> `\c' honor backslash escaping. Since the character becomes \c\\, the
>> subsequent `c' and `]' are literals.
>
> I assume this is only true for "to-be-escaped" characters, that is
>
> $ ` " \ <newline>
>
> like for ".."-strings? Of course only \ is of interest here.
>
> If that is true then the output of ksh93 for
>
> echo $'\c\d' |od -a -> 0000000 eot nl
>
> is wrong? It removes the \ every time.
The proposal leaves it implementation-defined. It specifically mentions
that you have to use \c\\ to represent <FS> to avoid ambiguity in the
backslash processing. Bash chooses to preserve the backslash before any
unrecognized escape sequence.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU c...@case.edu http://cnswww.cns.cwru.edu/~chet/
