> >sed "/^$/d" file
> >... doesn't look valid at all. eg, why double quote the de-limited
> >regex's? I never do that.
>
>That would be true on *nix. But when calling a batch file on Win2k (any
>Win32 OS, I think) you need the quotes. At least I have never been able to
>get it to work without the
>sed "/^$/d" file
>... doesn't look valid at all. eg, why double quote the de-limited
>regex's? I never do that.
That would be true on *nix. But when calling a batch file on Win2k (any
Win32 OS, I think) you need the quotes. At least I have never been able to
get it to work without them.
-NB
>I ran into a Win32 sed issue today while trying to use the port of sed from:
>http://unxutils.sourceforge.net/
>
>While trying to delete all blank lines in a file with the following cmd:
>
> sed "/^$/d" file
>
>it refused to work.
>
>But "super-sed" from: http://www.student.northpark.edu/peme
