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. Anyone have any idea of what may be causing
> this?
Normal grep and sed don't speak C-style escape chars. Use the -P option
for perl regex style in grep and it'll work. Dunno bout sed, but it all
gets tangled up in the matching against end-of-line $ anchor. See also "tr
-d '\015'", and of course d2u.
cheers,
DaveK
--
Can't think of a witty .sigline today....
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
