This is interesting. You called this an inplace edit, but it sounds a lot like it is
srill a transfer. Otherwise there would be no need for any backup extension. This
sounds essentially like an optomistic save, assuming that the procedure will finish
gracefully.I think that if you examine the
ActiveState docs suggest you can:
perl -pi '.orig' -e 's/bar/baz/' fileAto specify the .orig suffix but
That did not work for me.
perl -pi.bak -e 's/bar/baz/' fileA does! Thanks John
"John W. Krahn" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> Dave K wrot
Dave K wrote:
>
> perl -pi -e 's/foo/bar/' my_file.txt
> is supposed to do an inplace edit of my_file.txt, looping over each line,
> replacing foo with bar. Instead it merely stomps my_file.txt, effectively
> erasing it. Any body know why?
> Perl for cygwin, WinNt is the environment.
Yes, thi
JLW,
perl -pi -e 's/foo/bar/' my_file.txt
is supposed to do an inplace edit of my_file.txt, looping over each line,
replacing foo with bar. Instead it merely stomps my_file.txt, effectively
erasing it. Any body know why?
Perl for cygwin, WinNt is the environment.
David
"Jeff Westman" <[EMAIL PR
I got a priveate response to this posting, that may answer my original
question about using the mode "+<".
"I knew I ran into this before, just could not remember where. From the
docs (perlfunc open):
*
You can't usually use either read-write mode for updating tex
