On Jun 18, 5:54 pm, [EMAIL PROTECTED] (John Degen) wrote:
> >- Original Message
> >From: Paul Lalli <[EMAIL PROTECTED]>
> >To: [EMAIL PROTECTED]
> >Sent: Monday, June 18, 2007 6:47:05 PM
> >Subject: Re: Command line usage
>
> >On Jun 18, 1
##I have files read into $output_dir
if ($output_dir =~ "_Modified")
{
$allfile2 = $output_dir; #set allfile2 equal to output_dir to
keep
output_dir untouched
$_ = $allfile2; #set input string equal to allfile2 for
replacement
s/_Mo
>
>
>- Original Message
>From: Paul Lalli <[EMAIL PROTECTED]>
>To: beginners@perl.org
>Sent: Monday, June 18, 2007 6:47:05 PM
>Subject: Re: Command line usage
>
>On Jun 18, 10:50 am, [EMAIL PROTECTED] (John Degen) wrote:
>
>> I think I'm
On Jun 18, 10:50 am, [EMAIL PROTECTED] (John Degen) wrote:
> 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
--
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
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