On Wed, 10 Dec 2003 13:11:38 -0500, Paul Jarc wrote: > Eric Sunshine <sunshine@xxxxxxxxxxxxxx> wrote: > > This will not work correctly on Windows. At best, it will throw an > > error because FILE is locked (being read by sed) while the > is trying > > to open it for writing. > FILE wouldn't be read by sed; FILE.in would. > cp FILE.in FILE # for permissions (use -p?) > sed '...' < FILE.in > FILE # for content Indeed. I misread Akim's suggestion. -- ES
