Bruce Momjian <[EMAIL PROTECTED]> writes:
>> -e "s/[ ]NameData/\ name/g" \
>> -e "s/^NameData/\name/g" \
> What is that \n doing in there? It is certainly wrong. I am just
> wondering what is should be.
It's been like that since 1996, according to the CVS logs. I'm
surprised we have not had more reports of trouble --- either the shell
or sed might be deciding to translate that \n to a newline, although
evidently the consensus behavior is not to.
I zapped the gratuitous backslashes before the spaces, too, just
for luck.
regards, tom lane
