On Wed, Jul 30, 2008 at 9:47 AM, Dave Korn wrote:
> You omitted a vital qualifier from my earlier post ...
Sorry. I certainly had no intention of misrepresenting what you said.
I interpreted the newline thing not as a qualifier but as a separate
point, which I didn't attempt to contradict.
It
Dave Korn wrote on 30 July 2008 14:48:
> Mark J. Reed wrote on 30 July 2008 14:25:
>
>> On Wed, Jul 30, 2008 at 5:28 AM, Dave Korn wrote:
>>> Normal grep and sed don't speak C-style escape chars.
>>
>> Actually, sed does:
>
> You omitted a vital qualifier from my earlier post ...
>
>>> it a
Mark J. Reed wrote on 30 July 2008 14:25:
> On Wed, Jul 30, 2008 at 5:28 AM, Dave Korn wrote:
>> Normal grep and sed don't speak C-style escape chars.
>
> Actually, sed does:
You omitted a vital qualifier from my earlier post ...
>> it all gets tangled up in the matching against end-of-line
> jay3205 wrote on 30 July 2008 04:46:
>
>> I have a text file made in Windows, and I'm trying to replace all the
>> carriage returns with nothing. However, whenever I use \r or \n to
>> indicate >> a carriage return or newline in a grep or sed search string, it
>> is treated
>> as a normal r and
jay3205 wrote on 30 July 2008 04:46:
> I have a text file made in Windows, and I'm trying to replace all the
> carriage returns with nothing. However, whenever I use \r or \n to
> indicate
> a carriage return or newline in a grep or sed search string, it is treated
> as a normal r and normal n. A
jay3205 wrote:
I have a text file made in Windows, and I'm trying to replace all the
carriage returns with nothing. However, whenever I use \r or \n to indicate
a carriage return or newline in a grep or sed search string, it is treated
as a normal r and normal n. Anyone have any idea of what may
6 matches
Mail list logo
