-- Sane sicut lux seipsam, & tenebras manifestat, sic veritas norma sui, & falsi est. -- Spinoza > > >----- Original Message ---- >From: Paul Lalli <[EMAIL PROTECTED]> >To: beginners@perl.org >Sent: Monday, June 18, 2007 3:56:04 PM >Subject: Re: Command line usage > >On Jun 18, 8:40 am, [EMAIL PROTECTED] (John Degen) wrote: >> Thanks for your speedy reply Bob. I tried your suggestion, but the same >> outcome: the command fails without any complaints. BTW, the files didn't >> have extensions. They are three test files (plain text) containing >> respectively "love, live and luve". The actual command that I tried was perl >> -i -e "s/ve/ver/" *.* >> Any other ideas I might try? > >Windows has never let me replace files inline - that is, you can't not >give an extension for the -i option. You have to provide it with an >extension so that the original files are saved as backups. (However, >it's always given me an error when I've tried - not sure why you're >not getting one). > >try: >perl -i.bkp -e"s/ve/ver/" *.* > >You can also run a quick test to determine what * and *.* mean in >Windows by something like this: > >perl -le"print for @ARGV" * >perl -le"print for @ARGV" *.* > >Paul Lalli
Thanks Paul, I think I'm out of luck with this OS;) Your suggestion for creating a backup file gave the same result: no error, no change in the files. The output of 'perl -le"print for @ARGV" *' is * and the other is *.*. Funny though that sed *does* work. Best regards, John Degen -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] http://learn.perl.org/ ____________________________________________________________________________________ Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: mail, news, photos & more. http://mobile.yahoo.com/go?refer=1GNXIC -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] http://learn.perl.org/
